Skip to content

Sema: Add simulation of buggy Swift 3 typealias accessibility checking #6234

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

Basically if the underlying type of a typealias was dependent on
generic parameters from context, it wouldn't participate in
accessibility checking.

Turns out people were (accidentally) relying on this behavior, so
add a simulation of it in Swift 3 mode by ignoring such typealiases
entirely.

Fixes rdar://problem/29549232.

Basically if the underlying type of a typealias was dependent on
generic parameters from context, it wouldn't participate in
accessibility checking.

Turns out people were (accidentally) relying on this behavior, so
add a simulation of it in Swift 3 mode by ignoring such typealiases
entirely.

Fixes <rdar://problem/29549232>.
@slavapestov
Copy link
Contributor Author

@swift-ci Please smoke test

@slavapestov slavapestov merged commit 8bd5ddc into swiftlang:master Dec 12, 2016
@lattner
Copy link
Contributor

lattner commented Dec 13, 2016

Is it possible to produce warning when someone is depending on this in swift 3 mode?

@slavapestov
Copy link
Contributor Author

@lattner That's a good idea. I'll do that here and #6244 too.

@lattner
Copy link
Contributor

lattner commented Dec 14, 2016

Awesome, thanks @slavapestov !

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