Future of D 2.x as stable/bug fix, and what's next for D 3.x
russel at winder.org.uk
Fri Sep 4 06:57:15 UTC 2020
On Wed, 2020-09-02 at 09:19 +0000, Ola Fosheim Grøstad via Digitalmars-d
> But there is a difference between 1) having an ecosystem where
> many libraries and frameworks rely on stop-the-world-GC 2) having
> the option of using GC in application code (or maybe just in unit
My belief is that you end up with two runtime systems and standard libraries:
one for GC and the other for non-GC. Certainly doable for a community with
lots of people able to contribute, not so viable for a community with strictly
limited person effort available.
> It is possible to market a low-level programming GC strategy, if
> it is geared towards that specific use scenario.
> Especially if you consider mixed use, e.g. where the application
> use GC during initialization. But in those cases you might want
> the gaps on the GC heap to be available for malloc, or run
> compaction after initialization.
> Or just to have GC available for testing frameworks.
I fear that would be the worst of all worlds.
Dr Russel Winder t: +44 20 7585 2200
41 Buckmaster Road m: +44 7770 465 077
London SW11 1EN, UK w: www.russel.org.uk
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: This is a digitally signed message part
More information about the Digitalmars-d