fix: complete map<string, number> unboxing and literal boxing#174
Merged
Conversation
… fix literal boxing Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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.
Summary
getParameterMapInfoandgetThisFieldMapInfohelpers that return both key and value types (previously only key type was returned, value type was discarded)unboxStringMapGethelper to deduplicate ptrtoint→bitcast unbox logic across all 3 dispatch paths (local var, parameter, this-field)0.5) not being boxed ingenerateStringMapSet— the boxing code checkedgetVariableType()which returns null for constantsmap-string-number-param.ts(multiple gets with float values)Test plan
🤖 Generated with Claude Code