(no title)
ben-schaaf | 1 day ago
Smart pointers and containers are nowhere near memory safe, just enforcing their use gets you nowhere. `std::vector::operator[](size_t)` doesn't check bounds, `std::unique_ptr::operator*()` doesn't check null.
> Imo the strong point of rust is compile error if you try to use an obj after move (unlike c++ with undef behavior
The state of a value after being moved is defined by the move constructor. It is unspecified by the spec, but it's generally not undefined behavior.
pjmlp|1 day ago
It naturally doesn't cover C style programming in C++.
ben-schaaf|17 hours ago
Moldoteck|1 day ago
ben-schaaf|17 hours ago
pjmlp|1 day ago
The best is really to enable compiler specific hardening.