2 ms·
Well, it's not on me, because I'm often the user of someones library, framework, etc, and then it's up to whether it was concious or unconcious decision that th
by malkia 11mo ago
Well, it's not on me, because I'm often the user of someones library, framework, etc, and then it's up to whether it was concious or unconcious decision that the type behaved that way, and then you have to mix things to work together and you end up with this really "unspecified" way, hence you put some rules - "Don't do this" - don't use object after std::move, even if it might be allowed.
I'm still baffled.
- senderista 11mo agoWell they couldn't do much better without supporting destructive moves. Rust shows how simple move semantics can be when they're designed into the language.