4 ms·
The problem with the C solution is that you'll get hanging pointers. Try using i1 after the code above executes and you'll get a runtime error.
by rumcajz 8y ago
The problem with the C solution is that you'll get hanging pointers. Try using i1 after the code above executes and you'll get a runtime error.
- capitalsigma 8y agoYou can use C++ unique_ptr and turn on Clang warnings about "use after move", if you want that level of protection.
- a1369209993 8y agoEr, yes; that's what I said (or rather, hanging various things including but not limited to pointers). C only supported the typechecking part of this because it doesn't have any facilities for compile-time linearity checking. Linearity[0] and dependency[1] checking is what makes Rust a improvement over C, rather than yet another "let's reinvent C++, but slightly less awful" project. 0: "error: no implementation for copy〈T〉","error: no implementation for drop〈T〉"[2] 1: "error: cannot move/destroy x (of type T); y (of type T&'x) outlives it"