No, original go-trader used it, since quuckfixgo uses it, and during profiling it showed as a significant cost, so I wrote Fixed.Fixed
As a long ago game developer, we never used floating point - I'm sure things have changed now - but we always used fixed point integer, with lookup tables for sin, etc.
not really, except that all of them are going to zero, so fixed.Fixed should be sufficient :)
Also, at least in Go, it is fairly trivial to do: type Billions fixed.Fixed and then add operators to allow Fixed to be added, String() would add a B at the end etc. So 0.1 is 100 million, etc. Like I said, if you are…
As the author of Fixed, I'd like to make a few comments: 1. If you are above 100 billion, you are probably dropping the the 'fractions' and dealing with whole numbers. Most databases don't have their columns configured…
No, original go-trader used it, since quuckfixgo uses it, and during profiling it showed as a significant cost, so I wrote Fixed.Fixed
As a long ago game developer, we never used floating point - I'm sure things have changed now - but we always used fixed point integer, with lookup tables for sin, etc.
not really, except that all of them are going to zero, so fixed.Fixed should be sufficient :)
Also, at least in Go, it is fairly trivial to do: type Billions fixed.Fixed and then add operators to allow Fixed to be added, String() would add a B at the end etc. So 0.1 is 100 million, etc. Like I said, if you are…
As the author of Fixed, I'd like to make a few comments: 1. If you are above 100 billion, you are probably dropping the the 'fractions' and dealing with whole numbers. Most databases don't have their columns configured…