lysdexic@programming.devM to C++@programming.devEnglish · 1 year agoOn harmful overuse of std::move - The Old New Thingdevblogs.microsoft.comexternal-linkmessage-square2fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1external-linkOn harmful overuse of std::move - The Old New Thingdevblogs.microsoft.comlysdexic@programming.devM to C++@programming.devEnglish · 1 year agomessage-square2fedilink
minus-squareporgamrer@programming.devlinkfedilinkarrow-up0·1 year agoTo 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.
minus-squarecrispy_kilt@feddit.delinkfedilinkarrow-up0·1 year agoIn Rust, making something copyable is always explicit. I like that a lot.
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.
In Rust, making something copyable is always explicit. I like that a lot.