One class of bug can make you overwrite values in a map or get your code 'stuck' to a number, the other just gives you a (more) wrong number.
I know which kind of error would be preferred in a video game for instance.
One class of bug can make you overwrite values in a map or get your code 'stuck' to a number, the other just gives you a (more) wrong number.
I know which kind of error would be preferred in a video game for instance.
This is a common misconception: IEEE754 floating point arithmetic is not wrong or fuzzy or inherently inexact. It is very exact; it just has limited precision.
"Exactness" is a fuzzy term used in common english to refer to the concept of both precision and accuracy, or either really. It's not really used in mathematics.
Now whether that's accurate to you depends upon your application. But the numbers don't care.
It's not "different" terminology. It's the correct terminology. Which you should have down if you want to wisecrack at people.
You really just took a dozen words that were referring to the result of a calculation being wrong (as opposed to the real result) out of context to make them about floating point numbers in a vacuum.
Then after construing some new context, you tried to correct the straw man by giving an explanation in which you used pretty much all the terminology incorrectly.
Don't be surprised people come back at you in the same tone of voice if you leave an opening wide as a barn door.
I assume both of us are capable of constructing sentences using only precise mathematical language. This is not the place or time to flaunt that ability and correct others on things that are still perfectly understandable. We're not writing a paper.
Doing something like what you initially suggested would break that.
I did, personally, once have a bug in a script while working in finance, once upon a time. Working on a portfolio of test contracts with trillions of dollars in notional value, and I was off by a single penny. It was an easily found and fixed one-line bug due to truncation instead of correct rounding. But, yes. $1e-2 off on a portfolio worth $1e12 was enough to block release.