4 ms·
It’s faulty app logic, assuming an io error cannot occur accessing a filesystem. They’ll also crash if you have disk issues or driver problems. The important th
by ComputerGuru 3y ago
It’s faulty app logic, assuming an io error cannot occur accessing a filesystem. They’ll also crash if you have disk issues or driver problems. The important thing is they may not even realize they’re calling into a function or routine that can access the fs for something!
All io access needs to be recoverable or catchable for your app not to crash. You’d be surprised how much background fs activity there can be in apps (or indirectly triggered by apps!) all the time.
- brailsafe 3y agoThat and sandboxing effects with perhaps improperly accessed bookmark data I'm building a macos app now, and only because I wasn't catching fs access error did I realize I needed to handle folder access carefully when using bookmarks in core data.
- BeFlatXIII 3y agoI swear _Finder_ has this bug if you plug in a superannuated external HDD.
- dagmx 3y agoThis is one reason where I think Rust shines, and has even improved how I write C++. So many areas where rust makes me deal with a result or option that are easy to take for granted. It’s a strong reminder of the number of things we should be treating as possible error cases
- bpye 3y agoIt makes you do something, but if the consumer just does .unwrap() the end result is going to be the same.
- dagmx 3y agoSure, but a developer can also write any number of other code that’s irresponsible. At that point the language has done all it can for them, and the onus is on the developer to not be lazy. And when the crash happens, it’s obvious why