Skip to content

AST: Don't mangle weak/unowned as part of a property's type [5.0; ABI] #20818

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

Merged

Conversation

slavapestov
Copy link
Contributor

LibraryEvolution.rst stipulates that adding or removing 'weak',
'unowned' and 'unowned(unsafe)' is a resilient change if the type
is resilient. This means we should not mangle these attributes as
part of the accessor declaration.

LibraryEvolution.rst stipulates that adding or removing 'weak',
'unowned' and 'unowned(unsafe)' is a resilient change if the type
is resilient. This means we should not mangle these attributes as
part of the accessor declaration.
@slavapestov slavapestov requested a review from a team as a code owner November 28, 2018 01:24
@slavapestov
Copy link
Contributor Author

@swift-ci Please test

@slavapestov slavapestov changed the title AST: Don't mangle weak/unowned as part of a property's type AST: Don't mangle weak/unowned as part of a property's type [5.0; ABI] Nov 28, 2018
@AnnaZaks
Copy link
Contributor

This looks like a small change/bug fix. Is this impacting the convergence?

@slavapestov
Copy link
Contributor Author

@AnnaZaks it does not impact convergence but it is an ABI change

Copy link
Contributor

@AnnaZaks AnnaZaks left a comment

Choose a reason for hiding this comment

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

This is an ABI break, but the fix is small and isolated.

@AnnaZaks
Copy link
Contributor

Merging this because is an isolated fix which has an ABI impact.

@AnnaZaks AnnaZaks merged commit 715d1f9 into swiftlang:swift-5.0-branch Nov 29, 2018
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