On 2013-02-28 11:58, Dicebot wrote:
But issues with LDC and GDC need to be settled first. If D front-end in D
considerably harms any of those, it is a complete no-no, even if porting will be
perfect. Just not worth the loss.
Indeed, but even if LDC and GDC don't stop this from happening, I'm more worried
(as someone willing to write more of his programs in D instead of picking C++)
about stretching resources too thin on this one project, while there are tons of
more important things to do first (from my POV).
Let's see:
1) shared libraries (loading and being loaded),
2) GC, const refs, manual MM, containers managing their memory,
3) stop hiding AA's implementation,
4) improve libraries: bigint, xml, you name it,
...
n) rewrite the compiler's frontend.
I'm sure you can find a lot more to fit into the [5..n].
Even the infamous properties could rank higher than this migration, because,
frankly, I don't care what language the compiler is in, as long as I don't have
to install a JVM to use it. :)
