🍒 [5.7] Use AbstractStorageDecl::isSettableInSwift
to prohibit direct writes to optional
requirements
#42490
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.
StorageImplInfo
request. This approach has lead astray the conformance checker and might have had a negative impact on other code paths that expectisSettable
orsupportsMutation
to mean "has a setter". Also, this does not work for imported foreign declarations, since they bypass the request. Instead, use a forwardingAbstractStorageDecl::isSettableInSwift
method that special-cases optional requirements. This is a follow-up fix for a regression caused by 🍒 [5.7] CS:optional
storage key path components are read-only #42384.optional
storage components.optional
property requirement cannot be witnessed by a get-only property.AbstractStorageDecl::isSettableInSwift
to prohibit direct writes tooptional
requirements #42455