jextract/jni: Handle single-element tuples correctly#725
Merged
ktoso merged 2 commits intoswiftlang:mainfrom May 1, 2026
Merged
jextract/jni: Handle single-element tuples correctly#725ktoso merged 2 commits intoswiftlang:mainfrom
ktoso merged 2 commits intoswiftlang:mainfrom
Conversation
ktoso
approved these changes
Apr 29, 2026
Collaborator
ktoso
left a comment
ktoso
left a comment
There was a problem hiding this comment.
Sounds good, happy to drop the Tuple1
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
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.
Code generation fails when a single-element tuple is used. In Swift,
(T)is semantically identical toT, so attempting to access it via.0causes a compiler error.I've updated the generator to treat tuples with a single element as a single unwrapped value instead of a tuple.