Re:Simple, Fast and Safe Manual Memory Management [pdf]
by Animats on Thursday September 28, 2017 @02:01AM
(#15354991)
That's very clever.
It has most of the problems of garbage collectors that need to know object layout. "(void *)" will break this.
They don't mention I/O. If you have an I/O operation in progress, its buffer areas need to be locked. But the object-moving operation is lazy, so that's not too bad. You have to avoid getting into a situation where object-moving gets started, clashes with a pending I/O operation, and has to block. But this is Microsoft working on their own runtime, so they can fix I/O if needed.
It has most of the problems of garbage collectors that need to know object layout. "(void *)" will break this.
They don't mention I/O. If you have an I/O operation in progress, its buffer areas need to be locked. But the object-moving operation is lazy, so that's not too bad. You have to avoid getting into a situation where object-moving gets started, clashes with a pending I/O operation, and has to block. But this is Microsoft working on their own runtime, so they can fix I/O if needed.