Your view has been repeatedly refuted by Kahan and others. See page 25 of [1], page 1 of [2], page 22 of [3] for just a few examples. Conceptually, the reason the interval view is wrong is that if floating point values represented intervals, then their arithmetic would be incorrect. For example, the sum of an interval of width w1 and an interval of width w2 should be an interval of width w1 + w2. That, of course, is not how floats work at all. The correct view is that floats represent exact rational values and operations on them, instead of being the true mathematical ones – under which floats are not closed – compute the closest float to the true result of each operation.<p>[1] <a href="https:&#x2F;&#x2F;www.cs.berkeley.edu&#x2F;~wkahan&#x2F;JAVAhurt.pdf" rel="nofollow">https:&#x2F;&#x2F;www.cs.berkeley.edu&#x2F;~wkahan&#x2F;JAVAhurt.pdf</a><p>[2] <a href="https:&#x2F;&#x2F;math.mit.edu&#x2F;~stevenj&#x2F;18.335&#x2F;fp-myths.pdf" rel="nofollow">https:&#x2F;&#x2F;math.mit.edu&#x2F;~stevenj&#x2F;18.335&#x2F;fp-myths.pdf</a><p>[3] <a href="http:&#x2F;&#x2F;lyoncalcul.univ-lyon1.fr&#x2F;IMG&#x2F;pdf&#x2F;FloatingPoint.pdf" rel="nofollow">http:&#x2F;&#x2F;lyoncalcul.univ-lyon1.fr&#x2F;IMG&#x2F;pdf&#x2F;FloatingPoint.pdf</a>