Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dcl.init] Rephrase "user-defined conversion sequence" #2298

Merged
merged 2 commits into from Oct 9, 2018

Conversation

cpplearner
Copy link
Contributor

@cpplearner cpplearner commented Aug 12, 2018

  1. The conversion sequence is "governed by" the rules defined here ([over.best.ics]). Saying "conversion sequence" here will cause circular definition.
  2. Overload resolution selects a function, not a conversion sequence.

Also perform a minor reflow to keep "overload" and "resolution" in the same line.

1. The conversion sequence is governed by the rules defined here. Saying "conversion sequence" here will cause circular definition.
2. Overload resolution selects a function, not a conversion sequence.

Also perform a minor reflow to keep "overload" and "resolution" in the same line.
@@ -4328,10 +4328,11 @@
ambiguous, the initialization is ill-formed.
\item
Otherwise (i.e., for the remaining copy-initialization cases),
user-defined conversion sequences that can convert from the
user-defined conversion functions and converting constructors that can convert from the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The usual phrase to use here is simply "user-defined conversions", defined in [class.conv]. That's also what [over.match.copy] talks about.

@zygoloid zygoloid merged commit 28bd28f into cplusplus:master Oct 9, 2018
@cpplearner cpplearner deleted the patch-3 branch October 12, 2018 09:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants