3 ms·
All this may be true (I'm not the strongest C++ developer in the world, relatively limited exposure), however the Rust memory management via the type system fee
by no_wizard 3y ago
All this may be true (I'm not the strongest C++ developer in the world, relatively limited exposure), however the Rust memory management via the type system feels natural once you wrap your head around it. That idea is really good. I always hated dealing with `delete`, `free` and `malloc`.
Being able to offload all that busy work to the type system is just nice. There are definitely ergonomic improvements that could be made around this.
All the rest? I'll leave that to someone else to talk through, as I'm no expert here.
- germandiago 3y ago> however the Rust memory management via the type system feels natural once you wrap your head around it It disallows many valid patterns. That is why I recommend to take a look at Hylo programming language (before called Val lang) to see what I think it is a very good example of how to make a language safe without making the learning curve so steep and without a need for a GC.
- no_wizard 3y agoThe way Rust does it may disallow valid patterns, but it is not inherent to the idea
- bluGill 3y agoI.write c++ all the time, and I go months between needing new or delete. Unique_ptr is a wonderful thing. Not quite as powerful as rust's borrow checker, but it saves me a lot of thinking.