Others

@gparmer Tried my best to summarize everything. Let me know if I missed anything important out.

I've addressed most of the above comments, will investigate the others. I also got rid of the cFE_emu library, and used the existing c_stubs mechanism. @gparmer In terms of review...

@hjaensch7 Can you try and reproduce this?

Notes on the options presented here: 1) This option sounds nice, but I don't think it really works. We have to call libc's thread initialization routines to set up `pthread`...

As you can probably tell, I optimized for ergonomics, then collection performance, and have barely looked at optimizing memory overhead. I'm not sure your idea works. We need to track...

Okay we're down to 3 allocations after #34. I think we can go down to two, but it's slightly tricky because of how deallocating currently works. I think removing that...

Still tracking this. I think that this is probably more of an issue now that I got rid of the concurrent hash tables (since the speed of `Gc::new` is now...

Another complicating factor is the new support for unsized data. I found that compelling, but it complicates this since embedding unsized data in the `GcData` would be really really annoying

Yeah you can disable the lint. How does this handle the background thread in no std environments?

The architectural changes to allow the user to pass in a spawn function make me nervous. I have an inkling that the correct choice is to implement a switch for...