The worst thing you can do in non-unsafe Rust is perform an out-of-bounds indexing operation, or anything else that panics. The error you get tells you the panic’s exact location in the source code, down to the line and column. Meanwhile, C and C++ either don’t produce an error at all when accessing uninitialized memory (which is arguably the worst behavior), or it segfaults with zero extra info.
The only way to make Rust segfault is by performing unsafe operations, and those must always be clearly marked.
the point was not on the unsafe word, but a very specific feature of Rust that helps enclosing unsafe code where the compiler wouldn’t be able to 100% verify your logic. no such thing in C++. C++ does not even attempt to verify safety
your response is basically “get better at coding dumbass, I am the safety validator”
I mean, this is correct in many cases, unironically.
It should be one of the core purposes of a programming language to help humans to write the code they intend. If a language doesnt do that then it’s bad.
Am I bad at programming?
No, it’s the language thats wrong.
Except that many other languages have proven that C++ is simply terrible at providing meaningful errors.
The whole point of a segfault is that you can’t really know anything about it. Even in rust, when you get a segfault there is no meaningful error.
The worst thing you can do in non-unsafe Rust is perform an out-of-bounds indexing operation, or anything else that panics. The error you get tells you the panic’s exact location in the source code, down to the line and column. Meanwhile, C and C++ either don’t produce an error at all when accessing uninitialized memory (which is arguably the worst behavior), or it segfaults with zero extra info.
The only way to make Rust segfault is by performing unsafe operations, and those must always be clearly marked.
point is, Rust manages to give you not a segfault but a meaningful error almost all the time until you use unsafe
If you’re getting a segfault in C++, it’s also cause you used unsafe code. It’s just not officially enclosed in an “unsafe” block.
the point was not on the unsafe word, but a very specific feature of Rust that helps enclosing unsafe code where the compiler wouldn’t be able to 100% verify your logic. no such thing in C++. C++ does not even attempt to verify safety
your response is basically “get better at coding dumbass, I am the safety validator”
I wish there was something like that for SQL
We can always make a Rust Query Language
Feels like some arcane divination magic, I WANT IT
I mean, this is correct in many cases, unironically.
It should be one of the core purposes of a programming language to help humans to write the code they intend. If a language doesnt do that then it’s bad.
Valid languages:
That’s it
Brainfuck has entered the chat