Don wrote:
A lot of frustration has been expressed on the newgroup about lack of a
clear public plan for D2.0. I don't think we're in a position to create
a road-map. But, let's at least agree on which countries we'll probably
visit before we reach our final destination <g>.
Everyone knows there are a multitude of significant bugs in Bugzilla,
and most people have their pet list of minor language warts they hope
will be removed. But there's also some earthquake issues that have huge
implications. It's very disconcerting when some of them are introduced
in a casual manner. I think it would reduce a lot of frustation in the
community if we compiled an official list of the major ones. Here's a
few I came up with:
- Multithreading (I): Will Bartosz's proposal be accepted (in some form)?
- Multithreading (II): Will some form of message parsing be included?
- Operator overloading. "completely redone" (?)
- opImplicitCast
- is T[new] still going to happen?
- Phobos I/O -- Andrei has stated that he wants to completely rewrite it.
- Unimplemented features -- safe D, contract inheritance.
- Andrei once said that he wants to get rid of new (!)
- The Tango license issue needs to be sorted to the extent that Andrei
and Walter feel they can safely look at the Tango code; OR we can decide
that's not going to happen, and change the strategy for the Tango/Phobos
relationship.
The stuff on this list will either be implemented, or dropped. New
things could be added to the list. But we can gauge our progress towards
D2.0 by how rapidly the list shrinks with time.
Which other major issues have I missed? Things which, if they happen,
will probably require major spec changes, major library redesign, or
break large amounts of code. Let's get everything on the table.
Bartosz wrote the following on his blog:
Bartosz Milewski Says:
July 20, 2009 at 2:59 pm
To Álvaro: We’ve just had a conference–Andrei, Walter and I. We decided
that we have a deadline for D2, so we have to cut some features and
postpone them to D3. The race-free type system won’t make it–there just
isn’t enough time to implement and test it. There will be however a
stopgap solution for message passing in Phobos. It will be limited but safe.
Source:
http://bartoszmilewski.wordpress.com/2009/07/16/on-actors-and-casting/#comments
See comment 15.
Perhaps Walter, would like to publish or confirm what is on the final
list for D2. It would reduce confusion and rumour.
cheers
Nick B.
