On Tue, Apr 20, 2010 at 22:57, Lars Tandle Kyllingstad <[email protected]>wrote:
> Ok, it seems I understood you too literally. I think we mostly agree then. > Ideally, the constraint on Complex!T should act as a compile-time interface > that checks whether T *behaves* like a floating-point type. However, in this > case I personally think Complex!T should work equally well for all T or not > at all, and for the time being that means using isFloatingPoint. > And what defines a FP-like behavior, as opposed to merely numeric / defining mathematical operators? Having 0, 1, and something between 0 and 1?
_______________________________________________ phobos mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/phobos
