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.
When default @SwiftName rules are being applied, this update changes the Swift names of inner Java interfaces and of types declared within Java interfaces. Previously, if an interface Bar was declared within a type Foo or a concrete type Bar was declared within an interface Foo, they would be translated to a top-level type with Swift name Bar. This could cause problems if another inner type with the same name was also promoted. Now the Swift type name in each of these cases will be formed by concatenating the outer and inner type names: FooBar. This matches KMP's Swift naming of inner interfaces and of concrete types within interfaces. #2831
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
When default @SwiftName rules are being applied, this update changes the Swift names of inner Java interfaces and of types declared within Java interfaces. Previously, if an interface Bar was declared within a type Foo or a concrete type Bar was declared within an interface Foo, they would be translated to a top-level type with Swift name Bar. This could cause problems if another inner type with the same name was also promoted. Now the Swift type name in each of these cases will be formed by concatenating the outer and inner type names: FooBar. This matches KMP's Swift naming of inner interfaces and of concrete types within interfaces. #2831
Changes from all commits
5f37181File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing