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
[–] crispy_kilt@feddit.de 7 points 9 months ago (2 children)

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

[–] Miaou@jlai.lu 3 points 9 months ago (1 children)

Copy has a very different meaning between the two languages. In rust the equivalent of a c++ copy is a clone() call for anything non trivial

[–] BatmanAoD@programming.dev 3 points 9 months ago (2 children)

...which is also explicit.

[–] wosrediinanatour@mastodon.social 2 points 9 months ago (1 children)

@BatmanAoD @Miaou It is just what you are used to.
In C++ everything is a copy. Sometimes the compiler optimizes it away. clang-tidy may help. Having a clone() is very C-like.

[–] Miaou@jlai.lu 1 points 9 months ago* (last edited 9 months ago)

That's a common idiom but the default behaviour is still implicit copy, which, with VLAs and no smart pointers, makes things arguably worse than in c++

[–] Miaou@jlai.lu 1 points 9 months ago

I thought that was obvious as I mentioned a function call, but yes indeed

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