| ▲ | carlmr 2 hours ago |
| [flagged] |
|
| ▲ | _flux 2 hours ago | parent | next [-] |
| I think the difference is here: - If a compiled C++ program has unsound behavior, the program needs to be fixed - If a compiled safe Rust program has unsound behavior, the compiler needs to be fixed |
| |
| ▲ | bonzini 25 minutes ago | parent | next [-] | | > - If a compiled safe Rust program has unsound behavior, the compiler needs to be fixed Not really: the program still needs to be fixed, but fixing the compiler ensures that this unsound behavior never happens again for everyone. | |
| ▲ | jooops1 an hour ago | parent | prev | next [-] | | That's not completely correct. If the Rust or C++ compiler has a bug in both cases either the compiler has to be fixed or the program can be adjusted to work around said compiler bug If possible. However, It's fair to argue that the Rust compiler makes more assertions and is more complex, which results in a larger error surface. | |
| ▲ | afavour an hour ago | parent | prev | next [-] | | Which is better, surely? One fix for every program written in Rust vs everyone having to fix it themselves… | |
| ▲ | devmor 2 hours ago | parent | prev [-] | | > If a compiled safe Rust program has unsound behavior, the compiler needs to be fixed Can you provide an example of such a program that can’t be fixed at the program level like a C++ example? | | |
| ▲ | _flux 2 hours ago | parent [-] | | Sure, usually the program can be changed to avoid the issue, but the key here is that the Rust compiler is wrong and needs to be fixed. Once fixed, the actual program fix also falls in place, as it cannot be compiled anymore. |
|
|
|
| ▲ | krona 2 hours ago | parent | prev [-] |
| > You can be annoyed by Rust fanboys, sure, but the more annoying are the Rust haters, because the hate always comes from a place of ignorance. For what it's worth, Rust fanboys also seem just as vulnerable to their ignorance of C/C++ compiler extensions and tooling (e.g. sanitizers, bounds annotations, standard library hardening modes and so on.) which are just normal part of professional C/C++ use today. |
| |
| ▲ | afdbcreid an hour ago | parent [-] | | And are also woefully insufficient as proven in most sanitized & linted & fuzz-tested programs in existence (browsers and operating systems). | | |
|
