I consider the Swift compiler to be the poster child for “no one can write correct C/C++ and no one should try”. The compiler team has many extremely qualified C/C++ engineers, but the compiler/runtime have suffered from many crashes. Think of all the wasted time fixing them!
Such as...? I'm with you up until this point, but things like UAF are easier to avoid in Rust even if you're using custom allocators and data layout. (See generational indices for example.)
-
-
I'm thinking of things like "the system page size isn't what we thought it was" or "the condition for the conditionally-present tail-allocated bits was wrong and we didn't notice because we threw the load away until it ended up crossing into an unmapped page"
-
I agree Rust would help reduce the surface area of code exposed to these issues, and its ergonomics would probably encourage better management of invariants, but many of the issues we encounter seem like they're fundamentally in unsafe land
- 26 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.