Python is memory safe? Can’t you access/address memory with C bindings?

  • @Fal
    link
    fedilink
    English
    08 months ago

    Yes Rust is harder to write than C

    I would totally argue with this. Rust is way easier to write than C

    • @vext01@lemmy.sdf.org
      link
      fedilink
      28 months ago

      I agree for the most part, but writing data structures with shared mutable state can be a total pain in Rust.

      • @Fal
        link
        fedilink
        English
        -18 months ago

        How so? That’s like, the thing that makes rust awesome to write.

        • @vext01@lemmy.sdf.org
          link
          fedilink
          18 months ago

          It’s hard to get those kinds of data structures through the borrow checker.

          Try writing a doubly linked list.

          • @Fal
            link
            fedilink
            English
            -38 months ago

            It’s because it’s hard to make them correct. It’s not any harder to write it in rust than in C. Just C lets you do it wrong

            • @vext01@lemmy.sdf.org
              link
              fedilink
              18 months ago

              That’s not right.

              Try and write a mutable doubly linked list in Rust and you will find that it’s problematic for the borrow checker.

              Search online and you will find solutions that work around this using ‘RefCell’ (to delegate mutable borrows to runtime), or raw pointers with ‘unsafe’.

              • @calcopiritus@lemmy.world
                link
                fedilink
                08 months ago

                Both RefCell and unsafe are features of the language. That’s like saying python’s OOP sucks if you don’t use the class keyword.

                • @vext01@lemmy.sdf.org
                  link
                  fedilink
                  18 months ago

                  I’m not saying it sucks. I’m saying it can be less straight-forward than conventional languages, even for experienced programmers.

                  The borrow checker is fantastic, but there’s no doubt that it requires a new way of thinking if you’ve never seen Rust before.

    • Traister101
      link
      fedilink
      28 months ago

      I’d probably say it depends but I’m no Rust expert and I have no direct experience with C (though quite familiar with C++).

      Basically I’d expect writing C to be easy, but not safe. IE you can quickly and easily write C that compiles but has runtime issues. Rust for the most part will catch everything but logic issues during/before compilation meaning once the program runs you’ll have very high confidence in it’s runtime behavior leading to time spent “fighting the compiler” instead of figuring out wtf is going wrong at runtime.

      • Traister101
        link
        fedilink
        28 months ago

        I think primarily I don’t really care to argue about if it’s harder to write or not since it doesn’t really matter. I think the pros Rust provides are worth all it’s cons

      • @Fal
        link
        fedilink
        English
        -28 months ago

        IE you can quickly and easily write C that compiles but has runtime issues.

        So what’s “easy” about it then? Just getting something to compile? That’s not a very good measure of “easyness”.