Jordan Henderson

> Have you run the tests available in the project? I'll give it a try. Which tests are you referring to?

> In general, just to double check Yes, no crashes in the unit testing, nor with your original code ``` a = Pwhite.new(1802903, 1924888, inf).asStream; b = Pwhite.new(0, 10, inf).asStream;...

> Should think about how best to do that... Wonder if it is possible to add some bookkeeping to the internal allocater(s) so they can check their memory is being...

> What I linked to was an attempt to improve GC safety through an enhanced implementation. Not a test, so something a bit different. That's pretty cool! I was thinking...

> the more inadequate parts of the GC I think the GC in principle is pretty awesome, incremental tricolour — I can't quite see what flip does, is it a...

> > the bug I found with PyrGC calling its own methods in the constructor is an example of that. > > Did I miss that? I mentioned it in...

> Or is this addressing something else? So with this PR's initial bug, an pyrobject pointer was being incremented (actually decremented) and dereferenced. What I was suggesting was a way...

This conversation seems to have dwindled. Was there any thing I should be doing? As far as I can see, the only real way to test this is just to...

All CI tests are now passing.

@muellmusik don't suppose you'd fancy reviewing this and moving it towards merging.