this post was submitted on 18 May 2024
357 points (97.6% liked)

Programmer Humor

19623 readers
92 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 1 year ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
357
Not a Number (jemmy.jeena.net)
submitted 6 months ago by jeena@jemmy.jeena.net to c/programmer_humor@programming.dev
54 comments fedilink hide all child comments
 

Good price.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] victorz@lemmy.world 2 points 6 months ago (1 children)

Thoroughly confusing lol. I think I need to check the spec in order to grasp this. I feel like this has more to do with the typing system rather than nil itself, maybe. I'll see.

But yeah, this is nothing like null or undefined in JS, but more similar to NaN.

Thank you for trying to explain!

[โ€“] nickwitha_k@lemmy.sdf.org 2 points 6 months ago

Yeah... It's weird but I find it useful that it is, in a weird way. Treating it as an uncertainty means that one MUST explicitly check all pointers for nil as part of normal practice. This avoids NPEs.