Re:Taming the UB Monsters in C++
by steveklabnik on Monday March 31, 2025 @11:49AM
(#43536389)
To put an even finer point on it, crates.io releases are immutable, and so the only scenario in which you are even in a place where someone could try and modify a release is if you're depending on a git repo directly.
I believe the practical difference to 100% memory safety that Rust offers in theory, or the 99% memory safety you get in practice when using unsafe, compared to the 98% memory safety you can get today when writing decent modern C using abstractions such as string type and modern tooling is pretty irrelevant compared to all the other issues. Yes, the numbers are totally made up, but nothing I have seen so far convinces me that the reality is a lot different. Of course, there is a lot of old crappy legacy C code, and there will even be a lot of new crappy C code, but there will also be pretty bad Rust code. Now, if you like Rust, more power to you, I have no issue with people prefering Rust. But I think arguments for having to write in Rust for security reasons are mostly based on a series of fallacious arguments.
Re:Taming the UB Monsters in C++
by steveklabnik on Monday March 31, 2025 @12:16PM
(#43536705)
> Yes, the numbers are totally made up, but nothing I have seen so far convinces me that the reality is a lot different.
This is really what a lot of all of this comes down to, Herb and the committee feel like you do, others feel that the numbers won't be that good. We'll see in time!
> We'll see in time!
If by "in time" you mean last year then yes...
https://security.googleblog.com/2024/09/eliminating-memory-s...
Re:Taming the UB Monsters in C++
by steveklabnik on Monday March 31, 2025 @01:43PM
(#43537650)
I meant the opposite, the claim by sutter et al is that new C++ code that uses these new techniques will show the same results as this study shows for MSLs.
Oh I see. Yeah I agree. That's going to be a long time!
> Yes, the numbers are totally made up
Indeed.
> but nothing I have seen so far convinces me that the reality is a lot different
https://www.memorysafety.org/docs/memory-safety/#how-common-...
This is very well studied.
> Of course, there is a lot of old crappy legacy C code
Ahh... you don't make mistakes. I see.
All that said, I would love a language that had the same guarantees and performance without the complexity, but I don't see how that could work. There is definitely extra stuff in rust but the core capabilities come from the type system. Getting the same safety any other way would probably require a purely functional language which has performance costs in any implementation I am aware of along with a runtime being necessary. If you can afford that, then we don't need a new c, we have those languages.