[type-system] deduplicate fieldTypeToLlvm and add fail-loud default#750
Merged
[type-system] deduplicate fieldTypeToLlvm and add fail-loud default#750
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before
fieldTypeToLlvmwas duplicated identically inclass.tsandcontrol-flow.ts, each with a silentreturn "i8*"fallback that hides unrecognized types.After
No user-facing change. Internal refactor only.
Single
fieldTypeToLlvmintype-system.tswith explicit handling for every known type category (primitives, arrays, collections, unions, opaque types, function types, class/interface names) andthrowon truly unrecognized types.Description
fieldTypeToLlvm()fromtype-system.ts(29 LOC)class.tsandcontrol-flow.tsnow delegate to shared function via thin wrappers that handle enum check locally (enum check usesthis.isEnumType()which requires class context)methodReturnTypeToLlvmunion handling would be a behavioral change, so left as-is for a separate coordinated PRPartial progress on #710.