Should `Thread_map` become an independent library?
Dear memprof-limits maintainers,
motivated by recent discussions, I was wondering if it would make sense to maintain Thread_map
as its own library.
IIUC, it should work fine in OCaml 5, thus hence a motivation to split it.
Project like Coq need this functionality, so it'd be awesome to be able to depend on it. Note that Dune + dune-release
are precisely designed to release different packages from the same source tree.
It would also work if you decide that's not OK, we could then just vendor the library in Coq and wait until the whole package is available in OCaml 5; if so, please feel free to close this issue.