Aaron Stannard

> Should we consider going away from `ArraySegment` for internal storage and use `Memory` instead? On one hand it would be a bit of a yak shave, on the other...

> I don't think we will get any improvement switching over to Memory, even microsoft ReadOnlySequence still uses ArraySegment underneath. being able to work with new native APIs in .NET...

IMHO, there should be a mechanism for deleting data forever. If the data can be "forgotten" by removing a key when not using durable ddata, why should the durable version...

Keeping track of hard delete TTLs would require a separate "system CRDT" to track all of those, btw

Also, I'd limit the scope of the deletion behavior to keys - not individual entries inside more complex CRDTs such as ORMaps.

> TTLs are automatically reset (sliding window timeout) each time an entity is touched via a new subscription, update, or query. Also: that would not be a trivial change.

Going with a `Setup` is probably the best way to handle this in the short run.

.... Yeah this might be wrong. cc @IgorFedchenko ?

Any reason why we shouldn't take a reference on FluentAssertions inside the Akka.TestKit? cc @akkadotnet/core @akkadotnet/contributors

> Saw the referring PR: feels a bit like overkill to pull that in just for 1 line of code. But you might put more value on my previous comments....