On Sunday, 26 November 2017 at 08:49:42 UTC, Dmitry Olshansky
wrote:
If all of the code is 100% @safe (not system and not trusted)
you have a different language where write barriers would be
cheaper to implement.
Sadly you can’t “skip” write barriers in your @system code
because it may run as part of larger @safe. Which is where they
are the most costly.
I was thinking you would use a generational or precise GC for
@safe code and then fall back to the normal GC with
@system/@trusted code. Not sure if that's possible or not, but in
my head it would be a separate heap from the @safe code.
Certainly would be added complexity.
