Future of memory management in D

[SealabJaster]

On Wednesday, 17 November 2021 at 16:03:29 UTC, tchaloupka wrote:
> But then you'll start making workarounds for the GC, start to 
> manage memory manually here and there and then you realize that 
> you would probably be better without the GC in the first place. 
> Sometimes it just won't scale.

I wonder if we could make this a bit less painful if we had a 
thread-local GC by default, and another global GC purely for 
`shared` memory.

So `new Class()` might only stop the current thread, while `new 
shared Class()` might stop the world.