11–20 of 403 posts
The one link for those who think that 'Rewrite it All in Rust' will, well, settle any debates: https://github.com/rust-lang/miri/
Genuine question: Would you mind explaining to a dev that doesn’t know much (anything) about Rust, how does this settle any debate?
From the Miri github: > Miri is an Undefined Behavior detection tool for Rust.
Earlier quoted context omitted.
You linked an interpreter for some kind of internal compiler representation that the Rust compiler uses. What on Earth do you mean?
It's the old trope that some Rust code uses unsafe blocks so all Rust code is as unsafe as C.
The one link for those who think that 'Rewrite it All in Rust' will, well, settle any debates: https://github.com/rust-lang/miri/
The one link for those who think that 'Rewrite it All in Rust' will, well, settle any debates: https://github.com/rust-lang/miri/
Genuine question: Would you mind explaining to a dev that doesn’t know much (anything) about Rust, how does this settle any debate?
Yet, the linked repository shows a huge list of cases in which simple, documented use of Rust can cause Undefined Behavior (a.k.a. 'UB')
Pretty much every argument of Rust advocates against C/C++ boils down to either 'but memory safety' or 'but UB'.
Yet there are many convincing counter-arguments that boil down to 'but CompCert' or similar, and, as the linked repository shows, there might be at least some truth in there?
Earlier quoted context omitted.
You linked an interpreter for some kind of internal compiler representation that the Rust compiler uses. What on Earth do you mean?
It's the old trope that some Rust code uses unsafe blocks so all Rust code is as unsafe as C.
Getting people to adopt a new language can be a lot of work. I remember people claiming they missed headers files in Swift so they wanted to stick with Objective C.
Earlier quoted context omitted.
Genuine question: Would you mind explaining to a dev that doesn’t know much (anything) about Rust, how does this settle any debate?
From the original post > It’s not enough to rely on bug-finding tools From the Miri github: > Miri is an Undefined Behavior detection tool for Rust.
> The preferred approach is to use “safe” programming languages
“Safe”. Terms and conditions may apply.
The one link for those who think that 'Rewrite it All in Rust' will, well, settle any debates: https://github.com/rust-lang/miri/
You linked an interpreter for some kind of internal compiler representation that the Rust compiler uses. What on Earth do you mean?
That documented use of safe Rust can easily lead to UB, which this infernal 'internal compiler representation' demonstrates.
I'm not even sure what is even remotely confusing about that?
Earlier quoted context omitted.
Genuine question: Would you mind explaining to a dev that doesn’t know much (anything) about Rust, how does this settle any debate?
From the original post > It’s not enough to rely on bug-finding tools From the Miri github: > Miri is an Undefined Behavior detection tool for Rust.
In other words, from "safer languages are necessary" it does not follow that "safer languages are sufficient".
Earlier quoted context omitted.
You linked an interpreter for some kind of internal compiler representation that the Rust compiler uses. What on Earth do you mean?
> What on Earth do you mean? That documented use of safe Rust can easily lead to UB, which this infernal 'internal compiler representation' demonstrates. I'm not even sure what is even remotely confusing about that?