Hi Roberto,   the difficulty is that with realistic programs it is not easily determined, in which order operations are carried out.   Consider as an slightly exaggerated example   while(true) {     cin >> nextcmd;     switch (nextcmd) {         case 0:             std::move(ptr_i);             break;         case 1:             use(ptr_i);             break;     } }   Otherwise look - as alternative to move semantics - at the reloc discussion on this list for a way to also (in some fashion, at least in serial code) 'not being able to' use variables 'after' their content has been relocated from and watch some of the Cppcon videos about memory safety and approaches to improve it in C++: https://www.youtube.com/watch?v=ml4t-6bg9-M - Jim Radigan - -memory-safe C++ https://www.youtube.com/watch?v=l3rvjWfBzZI - Bjarne Stroustrup - Type-and-resource Safety in Modern C++ https://www.youtube.com/watch?v=ELeZAKCN4tY - Herb Sutter - Can C++ be 10x Simpler & Safer? https://www.youtube.com/watch?v=_pQGRr4P16w - Sunny Chatterjee - Closing the Gap between Rust and C++ Using Principles of Static Analysis   Best, Sebastian     -----Ursprüngliche Nachricht----- Von:Roberto R via Std-Proposals <std-proposals_at_[hidden]> Gesendet:Di 14.02.2023 18:02 Betreff:[std-proposals] Safety checks at compile time An:std-proposals_at_[hidden]; CC:roberto.romani_at_[hidden];  After an object is move from cannot be used!!! Or more generic after an object get unsafe cannot be used.