this post was submitted on 02 Nov 2025
286 points (96.7% liked)

Programmer Humor

27182 readers
1003 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
anzo@programming.dev
Feyter@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
286
Me, when doing error handling (infosec.pub)
submitted 1 day ago by cm0002@infosec.pub to c/programmer_humor@programming.dev
22 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] Strawberry@lemmy.blahaj.zone 5 points 1 day ago (1 children)

Rust programmers writing library code

[–] dejected_warp_core@lemmy.world 4 points 18 hours ago (1 children)

NGL, writing pure functions in Rust is fantastic. Writing responsible code that handles all the error conditions turns the "happy path" into hamburger. Even with the ergonomics of Result, Option, and even ?, code just sprawls and becomes a readability tradeoff. I'm only a few months into Rust at this point, and I have a lot to learn, but it's tempting to just .unwrap() and .expect() where I think it's unlikely to fail.

[–] Strawberry@lemmy.blahaj.zone 4 points 13 hours ago

That's honestly fine in your application code, but very frustrating to see in library code on crates.io. Nobody wants library code to panic over some nonessential functionality that the calling code could've recovered from.