[5.9][move-only] Ban partial reinitialization after consuming a value. #67146
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.
• Description: [5.9][move-only] Ban partial reinitialization after consuming a value. The language impact of this is that we want to be sure that partially reinitializing after consuming a value, results in an error:
The reason why we want to do this is that the original proposal said values were never partially initialized. We already have banned partial consumption, but we realized that this was another way to create a partially alive value. Given that, we want to go through a round of forum discussion at least before we put this out there. This closes the hole in the mean time.
• Risk: This is low risk since it only affects a corner case in a specific part of the noncopyable checker. So it cannot affect anything but noncopyable code.
• Original PR: #67145
• Reviewed By: @jckarter
• Testing: Added Swift tests
• Resolves: rdar://111498740