Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> One: I don't believe they have solved use-after-free. Marking memory freed and crashing at runtime is as good as checked bounds indexing.

It’s also something allocators commonly implement already.



One recurring theme about these new wannabe C and C++ replacements, but not like Rust, is that their solution is basically to use what already exists in C and C++ for the last 30 years, if only people actually bother to learn how to use their tools.

Unfortunely it is a bit like debugging, lets keep doing printf(), instead of take the effort to learn how to use better approaches.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: