I swear, every time I start to think that I go overboard with this sort of shit in my scripts for work, I either find another ridiculous edge case or a story like this comes out.
Comment on How One Uncaught Rust Exception Took Out Cloudflare
dhork@lemmy.world 3 weeks ago
Just because you’re writing in a shiny new language that never misses an opportunity to crow about how memory safe it is, doesn’t mean that you can skip due diligence on input validation, checking every return value and writing exception handlers for even the most unlikely of situations.
Lol
wizardbeard@lemmy.dbzer0.com 3 weeks ago
SeductiveTortoise@piefed.social 3 weeks ago
But at least it wasn’t a memory leak!!! 😭😭😭
Noja@sopuli.xyz 3 weeks ago
Memory leaks are logic errors, Rust can’t really prevent you from leaking memory.
calcopiritus@lemmy.world 3 weeks ago
It’s really hard to do without Rc (or similar) or unsafe.
Mechanize@feddit.it 3 weeks ago
You can leak data in perfectly safe Rust, because it is not a bug per se, an example is by using Box::leak
Preventing memory leaks was never in the intentions of Rust. What it tries to safeguard you from are Memory Safety bugs like the infamous and common double free.
socsa@piefed.social 3 weeks ago
Some memory leaks are logic errors, and this is honestly the irony of modern dynamic languages. I have actually gotten into the argument in interviews before - it is arguably safer (and better) to work from maximal static memory allocations with memory safe data objects than it is to implement dynamic memory algorithms just because they are fun coding problems.