On 2010-09-04 07:01, Walter Bright wrote:
Sean Kelly wrote:
I think write barriers in this context are calls out to the GC to
notify it
of reference changes, and these are generated by the compiler. A language
like D that can call inline ASM, external C routines, etc, simply can't
provide that guarantee. SafeD maybe.
Such write barriers are a performance problem, too.
What I've read about garbage collection techniques I got the impression
that you could implement a better and more efficient collector with
write barriers that would outweigh the performance loss that comes with
the barriers.
--
/Jacob Carlborg
