Re: How to make sure GC allocated resources stay around when used in C functions?

[Kagamin via Digitalmars-d-learn]

It must be scanned, so you shouldn't specify NO_SCAN attribute, 
it's for memory blocks, which are guaranteed to not hold pointers 
to GC memory, like ubyte[] buffers for i/o, so managed blocks can 
be safely collected without looking at content of NO_SCAN blocks.