Precise GC state

Ola Fosheim Grostad ola.fosheim.grostad at gmail.com
Sun Nov 26 09:05:12 UTC 2017


On Sunday, 26 November 2017 at 08:49:42 UTC, Dmitry Olshansky 
wrote:
> Sadly you can’t “skip” write barriers in your @system code 
> because it may run as part of larger @safe. Which is where they

Well, you can if you carefully lock the gc runtime or if you dont 
modify existing scannable pointers that points to existing 
objects (e.g. You could fill an empty array of pointers in unsafe 
code or pointers that point to something unscannable.), but all 
unsafe code would need vetting.

So it isnt impossible technically, but it is impossible without a 
change of philosophy.


More information about the Digitalmars-d mailing list