Phobo's migration
Joerg Joergonson via Digitalmars-d
digitalmars-d at puremagic.com
Wed Jun 22 09:44:25 PDT 2016
How bout Freezing Phobos, except for bugs and start migrating it
to Phobos 2.0?. This way a proper library can be built that
doesn't feel like a lot of stuff thrown together
haphazardly(think .NET).
This will be migrating Phobos over to use the new
constructs(nogc, safe, etc), remove the crust and just polish
things up. It could be added to the release and used "import p =
Phobos2;"
By the time it's finished D3 will be around and it could be used
for it. A committee can formed to decide what to include and to
design the structure of the library. Anyone can submit code.
This allows a clean break but and to learn, but not be shackled
by the past. It could go rather fast(months rather than years)
since most of the code is already written, it just needs to be
migrated properly(might might not require anything but copy and
paste for large amounts of code).
I know some people like to keep their old rusty cars on their
front lawns but it only tells everybody that they are stuck in
the past.
More information about the Digitalmars-d
mailing list