-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Sema] Diagnose use of implementation-only property wrappers #30939
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
Conversation
@swift-ci Please test |
Build failed |
Build failed |
LLDB broke @swift-ci test |
@swift-ci test source compatibility |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The failing test is expected to fail and that part of it should be removed. Hopefully it was just an over-reduced case.
Build failed |
Build failed |
We already ban all structs from declaring storage that comes from implementation-only imports. Until now we missed property wrappers, they were just dropped in deserialization. Resolves rdar://problem/59403617
4d44f08
to
efdfcee
Compare
I updated the PR with the test change that should resolve the OS X failure. Not sure what the Linux lldb failure is about yet, will see what happens. |
Build failed |
Build failed |
We already ban all structs from declaring that comes from implementation-only imports. Until now we missed property wrappers, they were just dropped in deserialization.
Resolves rdar://problem/59403617