Release: serverino - please destroy it.

[H. S. Teoh]

On Mon, May 09, 2022 at 12:10:53PM +1200, rikki cattermole via Digitalmars-d-announce wrote:
> On 09/05/2022 11:44 AM, Ali Çehreli wrote:
> > While we are on topic :) and as I finally understood what
> > generational GC is[1], are there any fundamental issues with D to
> > not use one?
> 
> This is not a D issue, its an implementation one.
> 
> We don't have write barriers, that's it.
> 
> Make them opt-in and we can have more advanced GC's.
[...]

In the past, the argument was that write barriers represented an
unacceptable performance hit to D code.  But I don't think this has ever
actually been measured. (Or has it?)  Maybe somebody should make a dmd
fork that introduces write barriers, plus a generational GC (even if
it's a toy, proof-of-concept-only implementation) to see if the
performance hit is really as bad as believed to be.


T

-- 
The best way to destroy a cause is to defend it poorly.