On Tue, 23 Feb 2010 07:04:22 -0500, Norbert Nemec <[email protected]> wrote:

Lars T. Kyllingstad wrote:
I completely agree. And I really don't think there is a lot more that needs to be done with the language -- I find D code as easy to read as Python code, and more elegant. The performance issue is a matter of allowing the compilers to mature, which will happen now that D2 is frozen.

True. Since IFTI is implemented, I don't see any major show stoppers. Of course, implementing a template expression numerical library a la Boost++ will be a stress test for D and I expect to find a number of rough edges, but that's actually part of the challenge of this project...

You might want to look at bugs 3474 and 2257, as well as the opIndex/opSlice problem. None of these are show-stoppers, but they do limit the api design and 2257 can be very exasperating.

Reply via email to