Skip to content

This update changes the Swift names of types declared within Java interfaces when default @SwiftName rules are being applied. Previously, a type Bar declared within interface Foo would be translated to a top-level type with Swift name Bar. This could cause problems if another interface Biz also declared an inner type Bar. Now the Swift type name will be formed by concatenating the interface and inner type name: FooBar. This also matches KMP's Swift naming of inner types within interfaces. - #2831

Open
copybara-service[bot] wants to merge 1 commit into
masterfrom
test_964107865

Conversation

@copybara-service

Copy link
Copy Markdown

This update changes the Swift names of types declared within Java interfaces when default @SwiftName rules are being applied. Previously, a type Bar declared within interface Foo would be translated to a top-level type with Swift name Bar. This could cause problems if another interface Biz also declared an inner type Bar. Now the Swift type name will be formed by concatenating the interface and inner type name: FooBar. This also matches KMP's Swift naming of inner types within interfaces.

…erfaces when default @SwiftName rules are being applied. Previously, a type Bar declared within interface Foo would be translated to a top-level type with Swift name Bar. This could cause problems if another interface Biz also declared an inner type Bar. Now the Swift type name will be formed by concatenating the interface and inner type name: FooBar. This also matches KMP's Swift naming of inner types within interfaces.

PiperOrigin-RevId: 964107865
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant