yolina

5 ms·

1. 1.▲
   by yolina 6mo ago

   You pretty much need lifetime tracking to make it foolproof. A quick dirty hack would be to have a static analyzer drop B from the symbol table after it sees std::move and give a warning, but that obviously wont catch other references to it
2. 2.▲
   by yolina 6mo ago

   destructive moves are required to make moves zero cost. Currently move semantics in C++ requires that A is left in a 'moved from, but valid state' which means that: 1. The compiler must still generate code that calls the destructo
3. 3.▲
   by yolina 6mo ago

   Some other language need to step up and rewrite/replace LLVM then, because no language that relies on a ~30 million loc backend written in C++ can ever hope to replace it.
4. 4.▲
   by yolina 6mo ago

   gcc seems to have full C++20, almost everything in 23 and and implemented reflection for 26 which is probably the only thing anyone cares about in 26. https://en.cppreference.com/w/cpp/compiler_support.html Funny