Gwenaëlle Lecat

Precise, no, but usually, walking through the files will do the trick, particularly in the `test` folder, were I happen to very often go back and forth between my tests...

I do not see any major blockers

Hello, `Irmin_pack` content's is not limited to `Irmin.Contents.String`, you should be able to use it with anything. I gave a look at your issue and it seems to stems from...

(I also got issues with ```contents_length_header = Some `Varint``` not working properly, you might want to set it as `None` if you meet problems with Repr and out of bound...

I did some changes to the branch: - Added a proper configuration - Added an `mli` file for `irmin_lavyek` - Updated `v` function to allow fresh stores - Corrected `set`...

A new example would be: ```ocaml #require "eio_main" #require "digestif.c" #require "irmin-watcher" #require "irmin-lavyek" #require "irmin.unix" module Store = Irmin_lavyek.KV.Make (Irmin.Contents.String) module Info = Irmin_unix.Info (Store.Info) let value = "pouette"...

Here are tasks that we might want to do (non-exhaustive): - Allow iteration (need to change lavyek) - Allow clear (need to change lavyek) - Stats, for benchmarking purposes (need...

I added the irmin-test suite on the lavyek side, I'll put my changes when ready not on master but on a branch named [irmin-lavyek](https://github.com/tarides/lavyek/tree/irmin-lavyek), in order to keep the main...

When testing changes on lavyek, I met a big issue with irmin-lavyek: Irmin creates 4 different lavyek stores, but if we do not separate them, they start corrupting each other....

I have rebased this PR over the eio branch now that the PR #2280 has been merged, however we will still have to make lavyek public to get the CI...