<br><br><div class="gmail_quote">On Tue, Apr 20, 2010 at 22:57, Lars Tandle Kyllingstad <span dir="ltr"><<a href="mailto:lars@kyllingen.net">lars@kyllingen.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
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.<br>
</blockquote><div><br>And what defines a FP-like behavior, as opposed to merely numeric / defining mathematical operators?<br><br>Having 0, 1, and something between 0 and 1?<br><br><br><br> <br></div></div>