www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - deprecation of "complex" floating point types

reply Francisco Almeida <francisco.m.almeida gmail.com> writes:
Are there plans to deprecate the built-in complex types soon?
Apr 02 2011
parent reply Moritz Warning <moritzwarning web.de> writes:
On Sun, 03 Apr 2011 00:48:29 +0000, Francisco Almeida wrote:

 Are there plans to deprecate the built-in complex types soon?
I assume they will be deprecated when a library replacement is feasible and implemented.
Apr 02 2011
parent reply Francisco Almeida <francisco.m.almeida gmail.com> writes:
== Quote from Moritz Warning (moritzwarning web.de)'s article
 On Sun, 03 Apr 2011 00:48:29 +0000, Francisco Almeida wrote:
 Are there plans to deprecate the built-in complex types soon?
I assume they will be deprecated when a library replacement is feasible and implemented.
I thought that the implementation of std.complex was already adequate?
Apr 03 2011
parent reply "Lars T. Kyllingstad" <public kyllingen.NOSPAMnet> writes:
On Sun, 03 Apr 2011 14:33:02 +0000, Francisco Almeida wrote:

 == Quote from Moritz Warning (moritzwarning web.de)'s article
 On Sun, 03 Apr 2011 00:48:29 +0000, Francisco Almeida wrote:
 Are there plans to deprecate the built-in complex types soon?
I assume they will be deprecated when a library replacement is feasible and implemented.
I thought that the implementation of std.complex was already adequate?
It is supposed to be, at least. :) If it's not, I'd very much like to know what's wrong or missing. -Lars
Apr 03 2011
parent Don <nospam nospam.com> writes:
Lars T. Kyllingstad wrote:
 On Sun, 03 Apr 2011 14:33:02 +0000, Francisco Almeida wrote:
 
 == Quote from Moritz Warning (moritzwarning web.de)'s article
 On Sun, 03 Apr 2011 00:48:29 +0000, Francisco Almeida wrote:
 Are there plans to deprecate the built-in complex types soon?
I assume they will be deprecated when a library replacement is feasible and implemented.
I thought that the implementation of std.complex was already adequate?
It is supposed to be, at least. :) If it's not, I'd very much like to know what's wrong or missing. -Lars
It can't happen until more work is done on the compiler's treatment of opEquals(). Note that there will be a large amount of work in removing it from the compiler. Moving AAs from the compiler to the runtime was horrific in terms of the subtle regressions it caused -- and it already used runtime calls for every operation it supported. Complex will be much, much worse.
Apr 03 2011