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.
Good price.
You ever have one of those moments when you just put 2 and 2 together, and also that you should have had that realization many years ago?
I just realized what NaN stands for...
This must be what people who get told "you can just wait for the shower water to warm up before hopping in" feel like.
The elephant and rope parable rings its bell of sound morals!
Not so much the realizing what NaN means; that's more relevant to that XKCD which I probably don't need to describe here.
"That makes it free, right?"
Not only that, it makes your entire purchase free due to NaN arithmetic.
But as you mention, NaN propagates.
So at checkout, your wallet will become NaN, as the shops money balance. Then it will spread to your bank account and before you realize what happens the whole banking-district is in flames.
no, it costs NaN, now remove NaN from your account...
...oh no
Technically it has a pricetag, so...
0*(NaN)... So does that mean the price IS a number?
Isn't any math operation involving NaNs also a NaN? At least that's my gut feeling.
Based on my frequent exploding and vanishing gradients, that would be a yes.
Thanks, relevant username!
Good point.
I suppressed most of my former js knowledge but I guess it's a string now.
In JS, it's just NaN if my browser's console is to be believed. I suspected it would probably be {object} for no clear reason
for no clear reason
JS That's the reason. The language has an awful type system.
I think its type system is "okay", I mean inherently dynamic typing is pretty error-prone. But its type coercion algorithms are bonkers. Also that whole "NaN ≠ NaN" business...
Also that whole "NaN ≠ NaN" business...
See that's one of the parts that is actually almost in line with other languages. In Go, for example, nil ≠ nil because nil is, by definition, undefined. You can't say whether one thing that you know nothing about is at all like something else that you know nothing about. It really should raise an exception at the attempt to compare NaN though.
If nil ≠ nil, how do you compare a variable to the literal?
You'd first check for nil values, then compare like normal. Extra step, yes, but it keeps you from hitting NPEs through that route.
You'd first check for nil values
What does this mean, if not the same as
then compare like normal
?
IIRC, a nil value can be checked against a literal successfully but not against another nil value. Say you want to check for equality of two vars that could be nil. You just need an extra if statement to ensure that you are not trying to compare nil and nil or nil and a non-nil value (that'll give you a type error or NPE):
var a *string
var b *string
...
if a != nil && b != nil {
if a == b {
fmt.Println("Party!")
} else {
fmt.Println("Also Party!")
}What I mean is that in JS you can't do NaN != NaN, not even variable != NaN. So you're not saying it's the same in Go, since you can do a != nil?
Kinda. nil is a weird value in Go, not quite the same as null or None in JS and Python, respectively. A nil value may or may not be typed and it may or may not be comparable to similar or different types. There is logical consistency to where these scenarios can be hit but it is pretty convoluted and much safer, with fewer footguns to check for nil values before comparison.
I'm other words, in Go (nil == nil) || (nil != nil), depending on the underlaying types. One can always check if a variable has a nil value but may not be able to compare variables if one or more have a nil value. Therefore, it is best to first check for nil values to protect against errors that failure to execute comparisons might cause (anything from incorrect outcome to panic).
ETA: Here's some examples
// this is always possible for a variable that may have a nil value.
a != nil || a == nil
a = nil
b = nil
// This may or may not be valid, depending on the underlying types.
a != b || a == b
// Better practice for safety is to check for nil first
if a != nil && b != nil {
if a == b {
fmt.Println("equal")
} else {
fmt.Println("not equal")
}
} else {
fmt.Println("a and/or b is nil and may not be comparable")
}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!
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.
If 0/0 is NaN, then does that mean 0*NaN = 0*0/0 = 0?
0*NaN = NaN
dirty onanists spilling their seed
Lennin died, with him died lenninism. Stalin died, with him died stalinism. Grandpa Onan, don't die!
In my language, onanování is masturbating. And onan is a mild insult insinuating that someone wanks a lot.
It's onanism in English. And it's rather stupid to call it that because Onan didn't masturbate, he used the pull out method to avoid getting his sister-in-law pregnant with his brother's kid. (yes, I know that sounds weird but that's the story)
I figure it is called that because both the pull-out method and masturbation for penis-havers involves spilling your seed somewhere outside of a woman's womb.
Yes, from a superficial viewpoint they are similar. And from a superficial viewpoint shooting a practice target is similar to shooting a person dead. It would be rather stupid to refer to target practice as murder.
I get your point, but considering that we got the word "Onanism" from the Bible I was thinking about some Christian denominations' views of why God wasn't happy with Onan in the Bible: because he ejaculated without trying to procreate. That is why I thought it was relevant to tie those two things together like that.
Onan's crime was greed not lust. He did not want to provide for Tamar or her potential children.
According to Wikipedia, Biblical scholars essentially agree with you, to the point
Bible scholars even maintain that the Bible does not claim that masturbation would be sinful.
which is pretty cool especially given my prior belief that most people agreed it was about lust. Wikipedia does also say that some Christian denominations have interpreted the sin to be as lust, though.
And Catholicism, at least, still doesn't like the ejaculation without procreation:
Since, therefore, the conjugal act is destined primarily by nature for the begetting of children, those who in exercising it deliberately frustrate its natural power and purpose sin against nature and commit a deed which is shameful and intrinsically vicious.
Small wonder, therefore, if Holy Writ bears witness that the Divine Majesty regards with greatest detestation this horrible crime and at times has punished it with death. As St. Augustine notes, "Intercourse even with one's legitimate wife is unlawful and wicked where the conception of the offspring is prevented. Onan, the son of Juda, did this and the Lord killed him for it."
(number 54 and 55 in a Pope Pius XI encyclical)
(I never thought I'd be discussing religion on programming.dev lol)
Onanieren in German
Onanovanie in Slovak.
Onanizál in Hungarian.
Central European gang rise up!
Onani in Swedish, which this image is from.
related: https://en.wikipedia.org/wiki/Some_Thoughts_on_the_Science_of_Onanism
by Mark Twain, btw. short read, and hilarious
...spilled his arithmetic overflow on the ground.
I like how the code adds a 0 at the start.
The code probably checks if the following number is greater than 10 (which fails for NaN) and otherwise adds a 0 in front.
It's priceless
Onani!
cost = "arm" + "leg";
lidl quality