The decision to dump the built-in complex and imaginary types in favour
of std.complex.Complex was made a long time ago, but nothing has
happened yet. So I have a few questions:
1. Is this still planned for D2?
2. In that case, when will it happen?
3. Are there any reasons why I shouldn't rep
On Dec 7, 09 22:40, Lars T. Kyllingstad wrote:
The decision to dump the built-in complex and imaginary types in favour
of std.complex.Complex was made a long time ago, but nothing has
happened yet. So I have a few questions:
1. Is this still planned for D2?
2. In that case, when will it happen?
Lars T. Kyllingstad Wrote:
> The decision to dump the built-in complex and imaginary types in favour
> of std.complex.Complex was made a long time ago, but nothing has
> happened yet. So I have a few questions:
>
> 1. Is this still planned for D2?
>
> 2. In that case, when will it happen?
>
>
Lars T. Kyllingstad wrote:
The decision to dump the built-in complex and imaginary types in favour
of std.complex.Complex was made a long time ago, but nothing has
happened yet. So I have a few questions:
1. Is this still planned for D2?
Far as I know, yes.
2. In that case, when will it ha
Andrei Alexandrescu wrote:
Lars T. Kyllingstad wrote:
The decision to dump the built-in complex and imaginary types in
favour of std.complex.Complex was made a long time ago, but nothing
has happened yet. So I have a few questions:
1. Is this still planned for D2?
Far as I know, yes.
2. I
