lysdexic@programming.devM to C++@programming.devEnglish · 1 year agoOn harmful overuse of std::move - The Old New Thingdevblogs.microsoft.comexternal-linkmessage-square11fedilinkarrow-up114arrow-down11
arrow-up113arrow-down1external-linkOn harmful overuse of std::move - The Old New Thingdevblogs.microsoft.comlysdexic@programming.devM to C++@programming.devEnglish · 1 year agomessage-square11fedilink
minus-squarecrispy_kilt@feddit.delinkfedilinkarrow-up0·1 year agoIn Rust, making something copyable is always explicit. I like that a lot.
minus-squareMiaou@jlai.lulinkfedilinkarrow-up0·1 year agoCopy 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
minus-squareFlorian Xaver@mastodon.sociallinkfedilinkarrow-up1·1 year ago@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.
minus-squareSpecialpatrol@feddit.uklinkfedilinkarrow-up0arrow-down1·1 year agoCpp should have done ref by default and had & for copy, but here we are.
In Rust, making something copyable is always explicit. I like that a lot.
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
…which is also explicit.
@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.
Cpp should have done ref by default and had & for copy, but here we are.