You pipsqueaks want memory safety? We'll show you memory safety! We'll borrow that borrow checker
  • @FizzyOrange@programming.dev
    8•2 months ago

    Yeah but I have written a lot of Rust and I have yet to use a single unsafe block.

    Saying “but… unsafe!” is like saying Python isn’t memory safe because it has ctypes, or Go isn’t memory safe because of its unsafe package.

    • @FalconMirage@jlai.lu
      1•2 months ago

      You don’t have to use unsafe C++ functions either

      C++ is technically safe if you follow best practices

      The issue, to me, is that people learn older versions of the language first, and aren’t aware of the better ways of doing stuff.

      IMO people should learn the latest C++ version first, and only look at the older types of implementation when they come across them

      • @FizzyOrange@programming.dev
        2•2 months ago

        C++ is technically safe if you follow best practices

        Yeah but it’s virtually impossible to reliably follow best practices. The compiler won’t tell you when you’re invoking UB and there is a lot of potential UB in C++.

        So in practice it is not at all safe.

        • @FalconMirage@jlai.lu
          4•2 months ago

          I agree

          I was only adding my opinion (that people should try to always use the latest version of C++, which is inherently safer, but still not 100% safe)