This is a really simple silly thing I just realized, but I noticed I have a lot code that looks something like this:
fn foo() -> Result<(), Error> {
// do something
}
fn bar() -> Option<()> {
let Ok(f) = foo() else {
return None;
};
}
I hated that if-statement. I realized today that I could simplify to:
fn bar() -> Option<()> {
let f = foo().ok()?;
}
And that cleaned up my code a lot. It’s a tiny thing, but when it’s okay to discard the error from the result, makes such a big difference when you have a lot of them!
That is a terrible time to throw away the error. Best to actually check for file not exists error and created the file only then. Other errors are important to see to debug why things are failing.
It is very annoying to have a tool tell you it failed to create a file when the file exists but it just cannot read it for some reason. You can spend ages jumping down the wrong rabbit whole if you don’t realize what is happening.
lol
This is unintentionally funny considering how
exists()is implemented (which is why we havetry_exists()now).Yeah that’s a good point. This is a special case where the file is simply caching runtime results so errors surrounding it not being read aren’t a big deal.