Skip to content

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

@sdkrystian

Description

@sdkrystian

[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.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions