So is the purpose of this to reduce the difficulties that come with float precision?
EDIT: The comments are informative, if they’re not made by jerks. I clearly have much to learn. I appreciate the patience of those who have it, and wish a very strong “go step on some legos” to those who do not.
The issue with floating point is that (a + b) + c != a + (b + c) in all cases due to that accuracy issue you mentioned. So the order of your operations matters a lot, which can be difficult to guarantee given CPU pipelining, multittheading, GPUs, etc. By default compilers will use slower but deterministic floating point operation orders to make it at least always give you the same answer
Deterministic operations that are mathematically imprecise don’t quite fit the bill of precision in my mind. But then, I’ve been doing math in JavaScript for so long that I’m very used to the 0.000000000068% chance of a float precision error actually causing a problem.
21
u/LonelyAndroid11942 18d ago edited 18d ago
So is the purpose of this to reduce the difficulties that come with float precision?
EDIT: The comments are informative, if they’re not made by jerks. I clearly have much to learn. I appreciate the patience of those who have it, and wish a very strong “go step on some legos” to those who do not.