Skip to content

[SwiftExtract] Construct .existential for 'any P' types - #901

Open
kateinoigakukun wants to merge 1 commit into
swiftlang:mainfrom
kateinoigakukun:pr-6cffee35ddcd5b8c28f5c0d7151358c155aa35f6
Open

[SwiftExtract] Construct .existential for 'any P' types#901
kateinoigakukun wants to merge 1 commit into
swiftlang:mainfrom
kateinoigakukun:pr-6cffee35ddcd5b8c28f5c0d7151358c155aa35f6

Conversation

@kateinoigakukun

Copy link
Copy Markdown
Member

The someOrAnyType translation had identical branches: both 'some P' and 'any P' produced SwiftType.opaque, so .existential was never constructed and 'any P' rendered as 'some P'. Construct .existential for the 'any' spelling. JExtractSwiftLib already handles .opaque and .existential in shared case arms, so its behavior is unchanged.

The someOrAnyType translation had identical branches: both 'some P'
and 'any P' produced SwiftType.opaque, so .existential was never
constructed and 'any P' rendered as 'some P'. Construct .existential
for the 'any' spelling. JExtractSwiftLib already handles .opaque and
.existential in shared case arms, so its behavior is unchanged.
@kateinoigakukun
kateinoigakukun requested a review from ktoso as a code owner August 21, 2026 13:30
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.

1 participant