Skip to content

Sema: Disallow usage of settable Self-returning storage requirements … #34214

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
merged 1 commit into from
Oct 11, 2020

Conversation

AnthonyLatsis
Copy link
Collaborator

…on existential base

In the future we could refine this rule so that we could safely make use of the getter and disallow interaction with the setter.

Although #34005 landed just 2 weeks ago, we could still use settable subscripts before that, so this is a source breaking change.

@AnthonyLatsis
Copy link
Collaborator Author

Should we aim for a specialized diagnostic for such assignments right away instead?

@AnthonyLatsis
Copy link
Collaborator Author

@swift-ci please smoke test

@AnthonyLatsis
Copy link
Collaborator Author

@swift-ci please test source compatibility release

@AnthonyLatsis
Copy link
Collaborator Author

@swift-ci please smoke test

@AnthonyLatsis
Copy link
Collaborator Author

@swift-ci please smoke test macOS

@AnthonyLatsis
Copy link
Collaborator Author

@swift-ci please test source compatibility debug

@AnthonyLatsis
Copy link
Collaborator Author

Looks like the source compat suite's deterministically acting up for some other reason :(

@AnthonyLatsis
Copy link
Collaborator Author

@swift-ci please test source compatibility

@AnthonyLatsis AnthonyLatsis merged commit 3bc381b into swiftlang:main Oct 11, 2020
@AnthonyLatsis AnthonyLatsis deleted the coself-mut branch October 11, 2020 12:38
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