Possible issue with Savable

I called it first thing. Both read and write I call first in my methods.

Yeah, and anyway I misunderstood how these classes work.

We should definitely catch the error because the writer just blasts things out without worrying about the dupes but the reader will have the dupes stomp all over each other since it stores them in a map when the object is first read.

It’s strange that a marshaling format doesn’t marshal them on the way out, too.