BridgeJS: Fix Dictionary bridging after Stack ABI refactor #594
+70
−74
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
kateinoigakukun
approved these changes
Feb 5, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Overview
PR #590 changed the stack storage from direction-specific variables to direction-agnostic ones, but the
Dictionarysupport code from PR #581 was not updated accordingly, causing compilation failures.Issue
After merging PR #590, the build fails with:
The Dictionary bridging code still referenced removed properties:
reservedTmpRetIntsreservedTmpParamIntsFix
JSGlueGen.swiftto use the new direction-agnostic stack APIDictionaryTypes.jssnapshot to reflect the corrected code generation