And yes, this is why Prone has shared mutable state, but you can't use it without "loading" the state into local pure data (explicitly makes visible that the original might change after loading) and you can't change it without "storing" a new version (explicitly makes visible that other consumers might have changed the original in the meantime), and offers compare-and-swap at a level of gigantic/nested container types. It's not quite general-purpose Software Transactional Memory, but it's as close as it needs to be, while still being something that should be possible to implement in a fast way most of the time.
(the not-fast use cases are possible but discouraged by the API)