Skip to content

jextract/jni: Support optional tuple return values 2#723

Merged
ktoso merged 7 commits intoswiftlang:mainfrom
sidepelican:optional_tuple2
Apr 27, 2026
Merged

jextract/jni: Support optional tuple return values 2#723
ktoso merged 7 commits intoswiftlang:mainfrom
sidepelican:optional_tuple2

Conversation

@sidepelican
Copy link
Copy Markdown
Contributor

This is an improved version of #720.

Currently, code generation is skipped when an optional tuple is used as a return value.
This PR addresses this limitation.

Support for optional tuples as parameters remains out of scope for this PR.

Thanks to the architectural improvements in #722, I'm now able to handle these tuples properly without the need for any workarounds.

@sidepelican sidepelican requested a review from ktoso as a code owner April 24, 2026 13:04
Copy link
Copy Markdown
Collaborator

@ktoso ktoso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Phone review but looks good, thank you!

@ktoso ktoso merged commit e7e9ba0 into swiftlang:main Apr 27, 2026
64 checks passed
@sidepelican sidepelican deleted the optional_tuple2 branch April 27, 2026 02:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants