Others
We know the entire lifecycle of handles and data, so we don't need Arcs necessarily
This is kinda awkward and needs refactoring, but we should do a double check of the `Lockout` before deallocating data. This will be pretty fast on the happy path, and...
Splitting off part of #28. We currently have a lot of memory overhead per `Gc`. We should aim to reduce that.
This is an internal mechanism, but it probably needs tested outside integration tests. After this is done, it should be audited carefully for races.
Place for people to comment about missing `Scan` implementations from `std`
It'd be cool if on the hot path instead of writing: ``` for $BIG__LOOP { // do work let x = gc.get() // gets a handle every loop -- potentially...
It might provide a performance boost if we add methods to `Scan` that are manually specialized methods of existing calls from the `collect` method. Right now we can't make the...
Since we have the whole `GcHandle` system, we have a nice way of figuring out if something can be moved or not. Could we exploit this to create a compacting...
It might be desirables for libraries to be able to set a "lower priority" configuration, that could then be overridden by executables "higher priority" configuration. Or perhaps we want scoped...
I don't think there are other good options. Hopefully someone proves me wrong!