Xe 
"No way to prevent this" say users of only language where this regularly happens
SOwOphie 🖥️👈 👀@cadey With the amount of willfully blindfolded slopfondling currently taking place, I wouldn't be too surprised to see someone rewrite a heap buffer overflow RCE in Rust very soon.
My bet would be on the bun people, but the competition is fierce.
Xerz 💗@sowophie @cadey (in fairness this should be fixed with the next generation trait solver, but who knows how long that'll take: https://rust-lang.github.io/rust-project-goals/2026/next-solver.html)
ananas@cadey Pretty surprised to see it being C++ instead of C.
And as a part of C++ committee, I can say with high confidence that we are working on making the language more safe.
I'm not sure if we can change the culture enough to stop people using practices that were known to be bad in the language for pretty much as long as it has existed though.
@ananas I really do respect the work that's being put into C++, it must be nearly impossible. But really this kind of stuff will continue until it's a compiler error :/
@cadey Yea, I don't see us eliminating this thing in the next decade at least, if ever.
Even if we somehow managed to get rid of the weird UB cases (towards which there is ongoing work), we can't force people to adopt all the changes even if compiler vendors made those default. Which in itself would probably break so much code that it's unlikely to happen, and a lot of the safeties we can and will add probably remain an opt-in, which is not ideal.
There is this profiles-thing coming that could finally allow us to finally do some subsetting for the language or enforce coding guidelines with actual compiler errors, but as there isn't a public implementation for the feature it's hard to say how far that can take us.