511
you are viewing a single comment's thread
view the rest of the comments
[-] Ephera@lemmy.ml 4 points 3 days ago

I know some of my programs used to have lines with just x.unwrap().unwrap().unwrap() or whatever, which is not pretty.

That goes away with experience, though. At least, I can't think of a reason why you'd nest three Results or Options. Normally, you would collate them right away.

The most you see in the wild is something like Result<Option<_>> to express that a check can fail, but even if it doesn't, then a valid result can still be that there is nothing there.

If you don't care that your program crashes (like .unwrap() does), then anyhow is the error handling library of choice. With it, you can just write a ? in place of an .unwrap() for practically any error type. And well, it automatically combines the errors, so you won't be writing ??? either.

[-] jackr@lemmy.dbzer0.com 2 points 3 days ago

yeah that was what I meant, I can see someone writing a mistake that requires ugly rust to solve and then believing rust is ugly because of it.

this post was submitted on 17 Dec 2025
511 points (96.0% liked)

Programmer Humor

27963 readers
1166 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS