756
Stop using floats (lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
[-] Ephera@lemmy.ml 2 points 6 months ago

My thinking is that a call to the safe division method would check after the division, whether the result is a NaN. And if it is, then it returns an Error-value, which you can handle.

Obviously, you could do the same with a NaN by just throwing an if-else after any division statement, but I would like to enforce it in the type system that this check is done.

[-] Lmaydev@programming.dev 2 points 6 months ago* (last edited 6 months ago)

I feel like that's adding overhead to every operation to catch the few operations that could result in a nan.

But I guess you could provide alternative safe versions of float operations to account for this. Which may be what you meant thinking about it lol

[-] Ephera@lemmy.ml 1 points 6 months ago

I would want the safe version to be the default, but yeah, both should exist. ๐Ÿ™ƒ

this post was submitted on 26 Feb 2024
756 points (95.8% liked)

Programmer Humor

19208 readers
1347 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