Re:Unsafe at Any Speed: Tradeoffs and Values in the Rust Eco...
by nindalf on Friday January 26, 2024 @02:02AM
(#39139646)
You have no idea what you’re talking about. You’re so confidently incorrect about Rust that there’s no point even trying to educate you. Good day.
Re:Unsafe at Any Speed: Tradeoffs and Values in the Rust Eco...
by dang on Monday January 29, 2024 @01:32AM
(#39173389)
Please don't post like this. We have to ban such accounts and I don't want to ban you.
See https://news.ycombinator.com/item?id=39173369 for more.
I have direct personal experience that opening an issue to politely ask this kind of design question is not always fine.
> Oh boy, hope you don’t open Vec in the standard library. It can’t be implemented without unsafe and it’s used by almost all Rust programs. I guess every program is unsound, according to you?
Based on past experience with LLVM undefined behaviour, yes, I think it's highly likely that every existing nontrivial Rust program is unsound in current Rust. But "depends on a standard library class that is currently implemented unsafely" will be much easier to fix in the future than "uses unsafe itself".
> Nor does it need to. Just because OP decided this is a problem doesn’t mean it actually is a problem. Find unsoundness and then you have something worth discussing.
Again, why use Rust at all if that's how you feel?