this post was submitted on 25 Nov 2023
29 points (96.8% liked)

C++

1718 readers
19 users here now

The center for all discussion and news regarding C++.

Rules

founded 1 year ago
MODERATORS
lysdexic@programming.dev
Nihili0@programming.dev
29
On harmful overuse of std::move - The Old New Thing (devblogs.microsoft.com)
submitted 9 months ago by lysdexic@programming.dev to c/cpp@programming.dev
22 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] DanielaKEngert@hachyderm.io 1 points 9 months ago (1 children)

@lysdexic @QuadriLiteral Eh, no. Really. Changing the value category disables RVO

[–] lysdexic@programming.dev 1 points 9 months ago (1 children)

RVO

I recommend you read the thread.

[–] DanielaKEngert@hachyderm.io 1 points 9 months ago (1 children)

@lysdexic I did.

[–] lysdexic@programming.dev 1 points 9 months ago (1 children)

It doesn't look like it, otherwise you'd be aware that the whole point of this submission is that casting return values with std::move disables RVO.

[–] DanielaKEngert@hachyderm.io 1 points 9 months ago (1 children)

@lysdexic You claimed otherwise:
"
These std::move invocations are harmless, as they only cast objects to their rvalue reference.
"
If you were right, we wouldn't have the motivation to look at this in EWG.

[–] lysdexic@programming.dev 1 points 9 months ago

If you were right, we wouldn’t have the motivation to look at this in EWG.

I am right. Not benefiting from RVO does not mean you're harming anyone.

Again, I recommend you read the submission and also the discussion.