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.

Sign up for GitHub

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

Jump to bottom

[dcl.init] vague wording for non-class initializer conversions #2374

Closed
Rakete1111 opened this issue Oct 28, 2018 · 3 comments
Closed

[dcl.init] vague wording for non-class initializer conversions #2374

Rakete1111 opened this issue Oct 28, 2018 · 3 comments
Assignees
@jensmaurer

Comments

@Rakete1111
Copy link
Contributor

[dcl.init]p17:

Standard conversions ([conv]) will be used, if necessary, to convert the initializer expression to the cv-unqualified version of the destination type; no user-defined conversions are considered.

As @zygoloid said, a sequence of standard conversions can potentially be arbitrarily long (temporary materialization -> lvalue-to-rvalue -> temporary ...).

We need some some rules to clarify and/or limit what standard conversions get used and how.
@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Oct 30, 2018
@jensmaurer
Copy link
Member

I'm not sure I understand the issue, and even if I did, this doesn't smell editorial to me.

@Rakete1111
Copy link
Contributor Author

The issue here is that it's unclear which conversion get used. It just says "standard conversions will be used, if necessary" which doesn't say anything ("just use standard conversions"). How many? Which one in which order?

Also, technically, because there are no restrictions, we could form a sequence of standard conversions through temp mat -> l-to-r -> temp mat -> ... (just an example).

@jensmaurer jensmaurer added the cwg Issue must be reviewed by CWG. label Nov 1, 2018
@jensmaurer
Copy link
Member

Editorial meeting: "A standard conversion sequence (xref conv) will be used, if necessary, to convert..."

@jensmaurer jensmaurer removed cwg Issue must be reviewed by CWG. decision-required A decision of the editorial group (or the Project Editor) is required. labels Nov 6, 2018
@jensmaurer jensmaurer self-assigned this Nov 27, 2018
@jensmaurer jensmaurer mentioned this issue Nov 27, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jensmaurer jensmaurer

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Rakete1111 @jensmaurer