On 2015-02-15 02:29, Alex Gilding wrote: > One cheap workaround for this would simply be to have a "nogc" function that > temporarily disables the GC around a piece of code. If you're crunching data > in > arrays, you probably want to isolate that operation in its own little > high-performance block anyway.
I would add some code to the garbage collector, in order to keep the array items protected. -- UNSUBSCRIBE: mailto:[email protected]?subject=Unsubscribe
