Jeremy Shaw

> However, the fact that sharedSecretCheck takes a set of secrets suggests that acid-state wants to support more complex setups where you have multiple clients connecting from multiple systems. In...

For what it's worth, I think some people consider 'multiple checkpoints per file' to be a misfeature. multiple events per file makes sense -- it saves a lot of overhead...

Using `tmpfs` would make that particular test Linux-only. Obviously that is still better than no test at all. It is certainly the most accurate test since the file system really...

We have casually discussed the idea of using something like mmap to allow developers to control what is currently in memory and what is currently on disk. Or perhaps something...

I think the primary reason for using appveyor at all is to ensure that the build works on Windows. That is somewhat important since we do have windows specific code...

This is patch where the copy was originally added. But I am not sure why it was added, https://github.com/acid-state/acid-state/commit/0dfb3941b20a2430323ec326b74401ce7ecbdb34 What purpose could that `Strict.copy` have? That is not the sort...

I think the problem here is that we have no suitable benchmark/testsuite to help give us confidence that this improves things more than it hurts things.

It looks like the subType stuff was added in this commit, https://github.com/acid-state/acid-state/commit/bcc6c86c3e91144cbd674cc420232b6f3efc078f But no explanation anywhere of why or what the intended use case is. If I had to guess,...

Something else to think about is the 'memory' backend. `acid-state` has a backend that stores the state in `memory` instead of on the disk. That, of course, means the state...

This is a limitation of the way SafeCopy is currently implemented. It is expected behavior -- but an error would be better. The short answer is "don't do that". The...