No, it is making a distinction between exact and inexact numbers, and uses arbitrary precision.<p>I don&#x27;t see it gain wide acceptance. If your problem is fixed-num, use a bignum library. If it is not, chances are you will meet a number that isn&#x27;t representable in this format very, very soon (1&#x2F;3, 1&#x2F;5, sqrt(2), PI, etc.)<p>The moment you do, you will have to decide to how many bits of precision you want to compute that inexact number. Problem is that you cannot make that choice, unless you know exactly what you intend to do with the number. I bet most users will choose a format that their hardware handles natively: IEEE.<p>There may be edge cases in numerical computing that benefit from this, especially when problems are ill-conditioned, but even there, I expect people to convert to conventional IEEE on the outside of their API. Also, I&#x27;m not sure there is much room in this space below quad-width floats (but I am not an expert)