▲ 47 ▼ Bugs Rust Won't Catch | corrode Rust Consulting - Analysis of Rust Coreutils (uutils) Bugs (corrode.dev) submitted 3 months ago by cm0002@literature.cafe to c/linux@programming.dev 22 comments fedilink hide all child comments
[–] khleedril@cyberplace.social -2 points 3 months ago (1 child) @davidgro @hunger Learn the three languages you are talking about before talking about them. Ill-informed thoughts impress no one. permalink fedilink source parent hideshow 2 child comments replies: [–] davidgro@lemmy.world 2 points 3 months ago* (1 child) I can't claim to have learned them well, but I have used Java and various Basics over the last 30+ years. Which parts of my comment do you disagree with? permalink fedilink source parent hideshow 2 child comments replies: [–] khleedril@cyberplace.social 2 points 3 months ago (1 child) @davidgro The way that #Rust guards memory is completely different to the way Java or Basic does. Rust is a fully compiled language suitable for systems programming, and the memory protection all happens at compile time; the runtime actually gains speed through the compilation process, rather than having the memory protection slow it down. The real difference is that the Rust compiler actually reads into the code it is compiling, rather than just making a mechanical translation. permalink fedilink source parent hideshow 2 child comments replies: [–] davidgro@lemmy.world 1 point 3 months ago That's true, it is a very different paradigm. I wouldn't go so far as to say that nobody thought it possible before Rust, but I agree it's much more effective and performant. permalink fedilink source parent
[–] davidgro@lemmy.world 2 points 3 months ago* (1 child) I can't claim to have learned them well, but I have used Java and various Basics over the last 30+ years. Which parts of my comment do you disagree with? permalink fedilink source parent hideshow 2 child comments replies: [–] khleedril@cyberplace.social 2 points 3 months ago (1 child) @davidgro The way that #Rust guards memory is completely different to the way Java or Basic does. Rust is a fully compiled language suitable for systems programming, and the memory protection all happens at compile time; the runtime actually gains speed through the compilation process, rather than having the memory protection slow it down. The real difference is that the Rust compiler actually reads into the code it is compiling, rather than just making a mechanical translation. permalink fedilink source parent hideshow 2 child comments replies: [–] davidgro@lemmy.world 1 point 3 months ago That's true, it is a very different paradigm. I wouldn't go so far as to say that nobody thought it possible before Rust, but I agree it's much more effective and performant. permalink fedilink source parent
[–] khleedril@cyberplace.social 2 points 3 months ago (1 child) @davidgro The way that #Rust guards memory is completely different to the way Java or Basic does. Rust is a fully compiled language suitable for systems programming, and the memory protection all happens at compile time; the runtime actually gains speed through the compilation process, rather than having the memory protection slow it down. The real difference is that the Rust compiler actually reads into the code it is compiling, rather than just making a mechanical translation. permalink fedilink source parent hideshow 2 child comments replies: [–] davidgro@lemmy.world 1 point 3 months ago That's true, it is a very different paradigm. I wouldn't go so far as to say that nobody thought it possible before Rust, but I agree it's much more effective and performant. permalink fedilink source parent
[–] davidgro@lemmy.world 1 point 3 months ago That's true, it is a very different paradigm. I wouldn't go so far as to say that nobody thought it possible before Rust, but I agree it's much more effective and performant. permalink fedilink source parent