Objects flushed before archiving

[ReedOei]

Suppose we run the following code:

A a = new A();
B b = new B();
a.f();

Suppose that $B$ has the default initializer, which calls __flushEntries();. In this case, a will get flushed, but it has not yet been archived. Then when we run a.f(), it will attempt to load from the archive, even though it is not there. This can result in several issues: in particular, it will make a's GUID the empty string.

We could save the state every time we flush: not sure if this is safe or the best solution.

[mcoblenz]

We might be able to fix this by restricting flushing to the end of the main contract's constructor (as opposed to all of them).