Anil Madhavapeddy
Anil Madhavapeddy
The underlying problem _might_ be that with a constraint like: ``` depends: [ "dune" {build & >="1.8.0"} ] ``` If dune is downgraded to 1.7.0, the package here should be...
Thanks for laying out all the options (cc @diml @rgrinberg as they may have Dune opinions on this matter). My instinct here is to keep to the conservative spirit of...
Discussed in opam dev meeting: putting this on the triage list for opam 2.2 to see if we can add this as a lightweight operator.
Confirmed to be because of too large a crunch, e.g. in the changelog.md file
Yeah, we need to detect this statically in the backend-specific linker script (it'll be different between xen and solo5 for example)
That's exactly right @philtomson. The issue is what lies behind the module types -- we need to build equivalent implementations of (e.g.) the network stack to support Async. There's one...
> Seems the semantics have subtle differences. Indeed. I've never tried it. Async is more conservative than Lwt in general, so it might just work. (note that it's Lwt embedded...
> am wondering if I should move it to the 5.1 section :) This is just fixing a bug in 5.0.0~beta1 isn't it? :-)
Your `opam why` output looks absolutely awesome. I want this in opam! :-)
@samoht: yes, see https://github.com/anmonteiro/ocaml-h2/pull/37