Thomas Gazagnaire

Recursive values are a bit annoying to deal with, as we need to remember which bits have already be seen. Most of the generic will currently explodes when dealing with...

Today we automatically unbox optional values and remove the field when the value is None. Need more control over it, and maybe allow to do the same thing for other...

See https://github.com/mirage/dyntype/blob/master/lib_test/test_value.ml

Test how the API in https://github.com/mirage/mirage/issues/1493 looks like

Release checklist

2

We can use this issue to track the list of things to be done before the release: - [x] have basic tests working on the TCP/IP stack [1](https://github.com/mirage/mirage-tcpip/pull/129) - [...

Re-enable easy x-compilation runes

1

See https://github.com/mirage/mirage-clock/pull/55 and https://github.com/mirage/mirage-clock/pull/52#issuecomment-1079933093

windows: FS.stats can raise `Sys_error`

1

On windows, it seems that `FS.stats`can raise `Sys_error`, which is not appropriately translated into an `Error` value (and so the caller has to wrap that call in a `Lwt.catch`statement)

See https://ci.appveyor.com/project/samoht/ocaml-git-7vmk0/build/1.0.104 ``` #=== ERROR while compiling mirage-fs-unix.1.2.1 ===============================# # opam-version 1.3.0~dev (98188f141dbeb429258f2b2c00f6240d0af02b84) # os win32 # command make test # path C:/cygwin/home/appveyor/.opam/4.02.3+mingw64c/build/mirage-fs-unix.1.2.1 # exit-code 2 # env-file C:/cygwin/home/appveyor/.opam/4.02.3+mingw64c/build/mirage-fs-unix.1.2.1\mirage-fs-unix-296-08c610.env #...