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

[class.copy.elision] Specification of when implicit move occurs is potentially confusing #3818

Open
sdkrystian opened this issue Mar 4, 2020 · 1 comment
Open

[class.copy.elision] Specification of when implicit move occurs is potentially confusing #3818

sdkrystian opened this issue Mar 4, 2020 · 1 comment
Assignees
@jensmaurer

Comments

@sdkrystian
Copy link
Contributor

[class.copy.elision] p3 says:

In the following copy-initialization contexts, a move operation might be used instead of a copy operation

Specifically, "might" makes implicit move sound optional to the implementation, since there is no specification as to what happens after overload resolution is performed.
@jensmaurer
Copy link
Member

It would be good to say that we actually call the constructor. We sort-of do that in [stmt.return], but {stmt.return.coroutine] is silent on that matter.

@jensmaurer jensmaurer mentioned this issue May 23, 2020
Closed
@jensmaurer jensmaurer self-assigned this May 23, 2020
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

Successfully merging a pull request may close this issue.

[class.copy.elision] Move specification of altered overload resolution jensmaurer/draft
2 participants
@sdkrystian @jensmaurer