Implement flush system about ink HOT 3 CLOSED

For the flushing system there will be two different ways of flushing.

Hard Flush

Flushes the cache and empties it.

If a contract A is calling another remote contract B that could potentially mutate the storage of A there must be a hard flush since B could write to the storage invalidating the cache of A.

Downside

A hard flush has the downside of A having to re-build the entire cache after the call of B returns.

Advantage

Whatever B does it is safe to perform a hard flush since nothing will invalidate cache if there is no cache. (:D)

Soft Flush

Flushes the cache and marks all flushes entries as clean.

If a contract A is calling another remote contract B that is not allowed to mutate the state of A (but besides that can do anything) then A can do a soft flush because anything that B could do won't invalidate the cache of A.

Downside

The run-time has to provide a way to allow A to call B in a way that the above mentioned guarantees are not invalidated by B.

Advantage

A soft flush has the advantage that A doesn't have to rebuild the entire cache after B returns.

from ink.

be555eb implements flushing for the fundamental SyncCell and SyncChunk types.
97696ec implements Flush for the remaining storage::{Value, Vec, HashMap, Stash}.

from ink.

This can be closed since it has been implemented and seem to be stable.

from ink.