[allocator.requirements.general] Fix the misuse of launder
#6452
Conversation
This file contains 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
|
See also #4553 (comment) CWG meeting concensus Nov 11: Not editorial. We definitely see an issue here. It might be whether the precondtions of We might not want to make the proposed change here until that issue has been resolved. |
|
@jwakely: If we made this an LWG issue, would LWG do anything with it other than immediately send it to CWG? |
tkoeppe
added
not-editorial
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 #4553.
I think the new-expression can render the contents in the storage indeterminate, and the
start_lifetime_as_arraycall can obtain the pointer to the first element even if the element is not within its lifetime.