Repository navigation
fix(swift): avoid duplicate callback metadata in struct bridges - #2016
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This branch was previously deployed
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.
Two modules exposing the same callback signature in struct fields emit duplicate Swift metadata and fail to compile together. Repro:
This applies the existing opaque method bridge to struct initializers and getters, including their JSI and native C++ converters.
The generated
@_spi(NitroCxx)bridge usesUnsafeRawPointerto borrow initializer arguments andUnsafeMutableRawPointerto initialize caller-owned C++ result storage. The regular Swift API stays typed.This works around swiftlang/swift#93318. Remove the opaque struct bridge once the minimum supported Xcode includes swiftlang/swift#93321.
Restores the original approach from the reverted fix: