[Property wrappers] Reject opaque result types when there is no initializer #32251
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…alizer. Fixes rdar://problem/63169705 / FB7699647.
|
@swift-ci please smoke test |
|
Does this only affect default initialization of property wrappers? It seems like this would also cause the crash when generating the memberwise initializer for @propertyWrapper
struct SomeWrapper<T> {
var wrappedValue: T
init(wrappedValue: T) { self.wrappedValue = wrappedValue }
}
protocol P { }
struct X {
@SomeWrapper var property: some P
} |
Test case from Holly Borla, thank you!
You're absolutely right! Fixed in the second commit, and added your example. Thank you! |
|
@swift-ci please smoke test |
1 similar comment
|
@swift-ci please smoke test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes rdar://problem/63169705 / FB7699647.