Vitaly Shukela

> you can add it, but I think it is conflict with the purpose of ZboxFS. > ZboxFS is privacy focused, so it is deliberately designed for only one process...

Also happens with `zbox = {version = "0.8.8", features=["libsodium-bundled"]}`: ``` #1 0x00007ffff7d7a535 in __GI_abort () at abort.c:79 save_stage = 1 act = {__sigaction_handler = {sa_handler = 0x555555977b00, sa_sigaction = 0x555555977b00},...

Found out about [`sodium_init`](https://github.com/jedisct1/libsodium/issues/555#issuecomment-307206290), then about [`zbox::init_env`](https://docs.rs/zbox/0.8.8/zbox/fn.init_env.html). Now it works. Is an `abort` (but not undefined behaviour) guranteed if trying to use Zbox without `init_env`? Otherwise `RepoOpener::open` should be an...

Why `init_env` isn't done automatically on each `RepoOpener::open`?

> As init_env is part of the basic API contract, I'd prefer use `debug_assert!` Can the function that is called to start using ZboxFS remain safe (non-`unsafe`) in this case?...

> In my opinion, &mut self has semantic meaning, that is, if you're going to change it you need to borrow it as mutable. `mut` should not be interpreted as...

It seems to fail to support working on multiple files even without threads. I get `zbox::Error::InTrans` if I try to work on multiple files simultaneously. `zbox::File` behaves as if it...

> Can you share your code about this issue? > One File cannot be mutated simultaneously, but multiple files should able to do that. ```rust fn main() -> Result {...

> One File cannot be mutated simultaneously, but multiple files should able to do that. > content manager needs to be exclusively accessed Is it a bug or by design?

Can two `zbox::File`s be sent to two threads that will write and finish multiple transactions on their files independently, without coordination? If no then it should be documented.