Every week or so there seems to be drama about some old dude shouting about how rust in the Linux kernel is bad. Given all the open hostility, is there easier way for R4L to continue their work?

  • toothbrush@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    6
    ·
    1 day ago

    I was only alluding to the fact that its a low level language like C, but with a more modern design and safety features, not anything specific, sorry!

    • cbazero@programming.dev
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      1 day ago

      I once heard that a major problem is that you have to disable or work around Rusts safety features once you write hardware interfacing code like a os kernel

      • Rossphorus@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        23 hours ago

        Not really. While working at the OS-level can typically require ‘unsafe’ operations a core tenet of writing Rust is making safe abstractions around unsafe operations. Rust’s ‘unsafe’ mode doesn’t disable all safety checks either - there are still many invariants that the Rust compiler enforces that a C compiler won’t, even in an ‘unsafe’ block.

        And even ignoring all of that, if 10% of the code needs to be written in Rust’s ‘unsafe’ mode that means the other 90% is automatically error-checked for you, compared with 0% if you’re writing C.