My D experience is only limited (mainly a C++ programmer) but something along these lines is how I have always imagined GC will sidestep the 'stop the world' problem as we move toward async/await programming models.
In theory you could use a region allocator for a pure function
and copy its result out.
This wouldn't be worth it in the general case but imagine worker
threads in a task pool. Pure functions executing message
in/message(s) out that did not significantly contribute to the
stop the world GC workload.
- Re: Componentizing D's garbage collector deadalnix
- Re: Componentizing D's garbage collector H. S. Teoh
- Re: Componentizing D's garbage collector Rainer Schuetze
- Re: Componentizing D's garbage collector Joseph Cassman
- Re: Componentizing D's garbage collector Joseph Rushton Wakeling
- Re: Componentizing D's garbage collector Joseph Rushton Wakeling
- Re: Componentizing D's garbage collector Timon Gehr
- Re: Componentizing D's garbage collector deadalnix
- Re: Componentizing D's garbage collector Andrei Alexandrescu
- Re: Componentizing D's garbage collector H. S. Teoh
- Re: Componentizing D's garbage collector Nicholas Londey
- Re: Componentizing D's garbage collector Sönke Ludwig
- Re: Componentizing D's garbage collector Chris Williams
- Re: Componentizing D's garbage collector Rikki Cattermole
- Re: Componentizing D's garbage collector Chris Williams
- Re: Componentizing D's garbage collec... Rikki Cattermole
