[expr.call] Add further forward references #6527
Merged
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
Eisenwave
force-pushed
the
fix-dangling-iref
branch
from
51f8375
to
a81ef47
Compare
Eisenwave
force-pushed
the
fix-dangling-iref
branch
from
a81ef47
to
cf580d3
Compare
|
@tkoeppe, this feels like a mild improvement to me. |
|
Indeed, thank you! |
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.
This paragraph is reaching ahead quite a bit; talking about scoped enumerations, eligible special member functions, non-trivial special member functions, etc.
This edit adds the relevant forward references. What originally motivated me is that the current wording contains
non-trivial destructor\iref{special}, which looked like a mistake. This forward reference is intended to apply toeligible.