C++

1773 readers

1 users here now

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

Rules

Respect instance rules.
Don't be a jerk.
Please keep all posts related to C++.

founded 1 year ago

MODERATORS

Nihili0@programming.dev

lysdexic@programming.dev

On harmful overuse of std::move - The Old New Thing (devblogs.microsoft.com)

submitted 11 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 11 months ago (7 children)

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

[–] Miaou@jlai.lu 3 points 11 months ago (4 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 11 months ago (3 children)

...which is also explicit.

[–] wosrediinanatour@mastodon.social 2 points 11 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 11 months ago* (last edited 11 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++

load more comments (1 replies)

load more comments (3 replies)