Zig vs Rust. Which one is going to be future?

I think about pros and cons and what to choose for the second (modern) language in addition to C.

@programming@programming.dev

  • calcopiritus@lemmy.world
    11·
    1 month ago

    A crate having the unsafe keyword doesn’t make the crate unsafe. The unsafe keyword just tells the compiler: “I know that what I’m trying to do may lead to memory safety issues, but I, as the programmer guarantee you that the codeblock as a whole is safe, so turn off some of your checks”.

    Using the unsafe keyword in rust is no much different than using a C library in rust.

    • PushButton@lemmy.world
      1·
      1 month ago

      It’s when you’re at the point of saying that unsafe is safe, it’s the point where you should just shut it up kid…

      • calcopiritus@lemmy.world
        1·
        1 month ago

        I don’t know why you are being so rude. I thought it was the rust community that was known for being toxic?

        It’s not my opinion on what the unsafe keyword means. That’s its purpose. Nobody ever wants to write unsafe code on purpose. The unsafe keyword was created to allow safe programs to be created in rust that wouldn’t be accepted by the strict rust compilers.

        In a Venn diagram, there are 2 circles: safe programs (1) and programs that are deemed safe by the rust compiler (2).

        Circle 2 is smaller than circle 1 and entirely contained inside it. However, there is no reason to not let people write programs from circle 1 that aren’t in circle 2. The unsafe keyword exists to enable programmers to write those programs in rust. However, it comes with a warning, now the programmer is the one responsible for making the program inside circle 1.