[intro.object] Clarify [intro.object]/3.1 #6196
Open
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
There should be no logical circular dependency.
frederick-vs-ja
force-pushed
the
providing-storage
branch
from
c0d613d
to
6c761cf
Compare
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.
Some reading may consider that "the lifetime of e has begun and not ended" can be interferred by the creation of the new object. It seems better to clarify that the condition only applies to the state immediately before the creation, and there should be no logical circular dependency on [basic.life]/1.5.
(Not sure whether the bullet should be applied to simultaneous implicit object creations.)
Fixes cplusplus/CWG#247 (perhaps).