- she/her
Principal engineer at Mercury. I've authored the Dhall configuration language, the Haskell for all blog, and countless packages and keynote presentations.
I'm a midwife to the hidden beauty in everything.
💖 @wiredaemon
twitch
twitch.tv/GabriellaG439discord
Gabriella439
discord server
discord.gg/XS5ZDZ8nnplocation
bay area
private page
cohost.org/newmoontwitter
twitter.com/GabriellaG439You must log in to comment.
in reply to @fullmoon's post:
you've probably seen me say it before, but I think == on floats is bad pl design generally. the majority of the times it's used one of the following is true:
- you're using the float as an int because your PL has bad number types
- you actually want to be testing if the values are within some epsilon of each other
- you're interested in bitwise equality and want NaN to be equal to NaN
I feel like the case were you're doing a numeric algorithm where IEEE-754 equality is actually the thing you want a much rarer.
Picking an appropriate epsilon value is also often nontrivial. There’s some pretty decent discussion of it here, in the context of figuring out what to do about it in Swift. https://github.com/swiftlang/swift-evolution/blob/main/proposals/0259-approximately-equal.md
