Robert Kawulak wrote:
From: Robert Kawulak 2008/12/5 Neal Becker <ndbecker2@gmail.com>:
How about, floating point is allowed, but the results may sometimes be surprising?
If the surprise consists of breaking the invariant, I'm not convinced... Moreover, isn't your proposition actually similar to the current state? Technically, there are no limitations in the library to
defining bounded<float> ("floating point is allowed"). But
From: Thorsten Ottosen Neal Becker skrev: prevent you from the advice in
the documentation ("don't use built-in floating point types with this library (until you really know what you're doing)") can be interpreted as "the results may sometimes be surprising".
Yes. I don't suggest changing anything.
I totally disagree. People have to deal with floats anyway. That is a seperate issue. The advic should be removed IMO, and bounded_float provided.
It should be provided, but Boost should first include some set of mechanisms to deal with the FP issues. They are too general to be implemented within this library and they are not tightly coupled with the concept of constrained types. I see this as an analogy to arithmetic overflows prevention, which is also too general and too orthogonal to this library. Best regards, Robert