this post was submitted on 18 May 2024

360 points (97.6% liked)

Programmer Humor

19488 readers

1092 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

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 1 year ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

360

Not a Number (jemmy.jeena.net)

submitted 5 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 5 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 5 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.