Unexpected GC behavior with Tuple about cello HOT 5 CLOSED

Thanks for the detailed report. I will have to dig a little bit deeper to see exactly what is wrong but I think this is to do with the fact that tuples are not real value types and actually only contain pointers to the objects inside of them (tuple was a terrible name in retrospect since you assume it will be a value-like type) so it may be pointing to a stack allocated object which get cleaned up or overwritten or has some other odd behavior...

Either way it doesn't seem good to use a tuple as a key type. Perhaps you can use an Array instead for now until I find out what exactly is wrong?

from cello.

You're welcome!

I tried to take into account that Tuples were just arrays of pointers by allocating everything I put in them on the heap with new, like in my example. What I was surprised by was that despite Tuple implementing Mark an object being in a Tuple didn't seem to count towards its reachability.

Thanks for the suggestion to use Array. I'll do that.

from cello.

After a bit more investigation I think this is actually a bad bug to do with the GC. Looking into it more now...

from cello.

Okay I think I have a temp fix included in a0fa757 but I will probably need to look again at some point to clean up the interface to the GC to make this sort of thing easier and more efficient. Many thanks for the bug report!

from cello.

Great! You're very welcome. Your latest commit fixes the bug for me. 👍

from cello.