Per thread heap, GC, etc.

[Markk]

On Friday, 14 May 2021 at 16:59:58 UTC, H. S. Teoh wrote:

> IMO that impression is misleading, because those who are happy 
> with the GC are silent and you don't hear from them, and the 
> ones complaining about it are the vocal minority.

Yes that could well explain a good proportion of it.

But then I do find the argument valid for many application 
scenarios. And I would probably think less of it if I hadn't 
watched many of the Dconf and other sessions, where the topic of 
non-GC memory safety seems very dominant. There is this constant 
"the grass is greener over there" vibe coming across, with nods 
to Rust et al.

All the proposals I encountered so far (@life etc.) always want 
to ditch the GC entirely (as a global application choice) and 
that's something that I think will be very damaging to D's power 
and ecosystem. It will effectively ban all the existing D code 
base from these applications and make the life so much harder for 
those that want to support both worlds. I guess there will be two 
stdlibs and two of everything, or if unified it will be crippled.

The proposal I made here might fix this. If it works, it is the 
best of both worlds, combined.

_Mark