DefiniteInitialization: correctly handle implicit closures in initializers of derived classes. #38271
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
…izers of derived classes. Support for implicit closures was already added in c452e4c: init() { bool_member1 = false bool_member2 = false || bool_member1 // implicit closure } But this didn't work for initializers of derived classes. rdar://66420045
|
@swift-ci test |
|
Build failed |
|
@swift-ci test macOS |
1 similar comment
|
@swift-ci test macOS |
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.
Support for implicit closures was already added in #35276:
But this didn't work for initializers of derived classes.
rdar://66420045