swap-and-destroy called too eagerly #8950
Merged
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.
The error exhibits as:
triggered by dlang/dmd#16314 and is blocking it.
The trouble is Tuple.opAssign() selects swap-and-destroy when one of the arguments is const/mutable/shared, and so cannot be assigned to. This fix causes the opAssign branch to be taken instead.
The test case is a bit difficult to come up with, as it comes with 16384.