Andrew Jeffery

Having looked through the code a bit I think I'd plan to add this through the following changes: - Create a new `TxDiff` type that is similar to a `ReadOnlyTx`...

Yes, I think it should be ok to do it so that they only pay for it when they ask, otherwise we basically continue with similar logic to now.

Note: I expect the metrics for memory usage to increase as the logging sample now maintains an additional index so that we can properly test this new behaviour.

I like the idea of this becoming a part of the library as it seems like a very easy thing to trip up on otherwise, I wonder if there are...

Since there seems to be quite a large difference between the js and rust output here I'm thinking we have ourselves a bug...

I've had a go at removing the queue from the Rust backend [here](https://github.com/automerge/automerge-rs/pull/206). Pretty simple and still allows wrappers to handle the queuing logic. One question I have is around...

As a middle ground could we store microseconds? This should give us enough years and quite a bit of precision. Datacenter networks can be in microseconds and I think some...

Ah, I was considering the timestamp type [here](https://github.com/automerge/automerge-rs/blob/9fb8666028e80b05244a8ab8fc2592e04b379c62/automerge-frontend/src/value.rs#L33). Since this is a user value I was expecting them to choose to just truncate the precision they want. If this is...

For use cases I'd potentially have one for example storing time measurements of documents in automerge. This means they could be network latencies or internal computation operations, likely taking less...

Definitely! I really like the concept of having a model be explorable and not having to run the checker every time to explore it would be great. I imagine sharing...