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

C++

1718 readers
20 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
[–] porgamrer@programming.dev 10 points 9 months ago (10 children)

To me it's not really excitement so much as "oh god how do i make this ridiculous language do the correct thing".

I'm way more scared of rogue implicit copy constructors. I wonder if cppfront has any plan to fix problems like implicit copy and pessimising move.

[–] crispy_kilt@feddit.de 7 points 9 months ago (7 children)

In Rust, making something copyable is always explicit. I like that a lot.

[–] Specialpatrol@feddit.uk 3 points 9 months ago (1 children)

Cpp should have done ref by default and had & for copy, but here we are.

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

Cpp should have done ref by default and had & for copy, but here we are.

That would defeat the goal of making it backwards-compatible with C.

load more comments (5 replies)
load more comments (7 replies)