std.complex

[Lars T. Kyllingstad]

On Tuesday, 26 November 2013 at 13:32:22 UTC, John Colvin wrote:
>
> Just had a chat with one of our local numerics experts: He 
> agreed that hidden special casing that breaks standards 
> compliance is bad and that whatever the solution was it should 
> be explicit.

I don't think we should worry too much about standards 
compliance. A library Complex type is quite different from a 
hardware floating-point type.