Simon Cruanes
Simon Cruanes
It seems like all the state is now thread-local in `Caml_state`, but imho recording backtraces should be a global (atomic?) boolean. I've never wanted to record backtraces only in some...
The obvious choice to me is that backtraces are a global setting. It's consistent with setting it with OCAMLRUNPARAM. I'm also having a hard time imagining a use case for...
@gridbugs https://github.com/ocaml/opam-repository/issues/23789#issuecomment-1882107221 I hope you're not suggesting that, if a user publishes a new version of their package one day, they might have to wait months before having it available...
A quick calculation shows that in the worst case, each array could be 500 * 200 * 8B = 800kB of data. On average it might be 250 * 100...
There's no need for `ppx_blob`, a tiny bit of dune magic can suffice. But overall I think it's fine to do this!
I think it'd be interesting! Displayed like a git log, perhaps? On the web I think there's a wasm version of graphviz that can be used.