You pipsqueaks want memory safety? We'll show you memory safety! We'll borrow that borrow checker
  • Ephera@lemmy.ml
    0·
    2 years ago

    The inherent problem with this kind of solution is that if you don’t break backwards compatibility, you don’t get rid off all the insecure code.

    And if you do break backwards compatibility, there’s not much reason to stick to C++ rather than going for Rust with its established ecosystem…