serializing llrb with gob causes a runtime error: invalid memory address about gollrb HOT 4 CLOSED

Feel free to pm me if you need anything to debug.

from gollrb.

You can't encode every Go struct. The struct needs to have encoding methods or contain public fields.
Tree is not meant to be encoded. There is no need. If you want to save a tree, just save its elements.
When you load it, just reinsert the elements in the tree.

from gollrb.

Thanks for the reply. I was simply playing with gollrb. It seems to me that it would be faster to read from disk in gob encoded than reading and re-inserting elements in the tree. Lets say that you want to save the current state of the tree so you can process it later. Also, wouldn't the rpc package fail if you try to send this since they rely on gob?. Thanks again.

from gollrb.

It is marginally faster to save the tree structure, rather than to save the elements and reinsert them.

The new Root() method exposes the root element and you can serialize it with whatever (gob, json, etc.)
When de-serializing, use SetRoot.

Note that the comparison function cannot be serialized.

from gollrb.