D2 Blockers?
Brad Roberts
braddr at puremagic.com
Mon Aug 16 21:47:37 PDT 2010
On 8/16/2010 9:33 PM, dsimcha wrote:
> What are the current blockers to merging non-ancient versions of D2 into GDC?
> I've been quietly following the project and noticed that:
>
> 1. It's actively being worked on.
>
> 2. D1 is up to date.
>
> 3. There were a bunch of issues w.r.t. druntime, but these seem to be resolved.
>
> 4. A new version of D2 hasn't been merged in ~1 month, even though the
> project is generally active.
>
> 5. There was some concern about breaking the currently working 2.019. IMHO
> this is **completely** unwarranted, as support for such an outdated D2 version
> is probably **completely useless** to just about everyone. Probably no
> non-trivial code that compiles for 2.019 will work on the latest version or
> vice-versa, and the only code that's still written for 2.019 is really old,
> unmaintained code that noone cares about. IMHO until you're at least close to
> the latest version, you should just break older versions with reckless abandon
> to march towards getting recent, useful versions working.
Along similar lines, I'd dearly love to see gdc+d2 sitting on top of the
druntime rather than maintaining an internal, ever drifting, fork. To that end,
I'd welcome patches (preferably small baby-step type patches, not huge lump sum
code drops) to narrow the differences.
More information about the D.gnu
mailing list