Raphaël Proust
Raphaël Proust
Thanks a lot!
@patricoferris is this fixed by https://github.com/ocsigen/lwt/pull/1033? It's blocked by https://github.com/janestreet/ppx_let/pull/16
If ocaml-ci has some openbsd runners, would it make sense for oapm-repo-ci to also have some? (ping @shonfeder what do you think?)
@mtelvers so we should have ``` [ "clang++" ] {os = "openbsd"} ``` ? And we should probably not have anything for freebsd then?
O asled pffbamd amd @thatportugueseguy doesn't have a way to reproduce (and it seems like ocamlco doesn't do openbsd anymore anyway). I think we should close this PR and wait...
@MisterDA thanks!
proposal: replace the `awaken ~ordering` function with two distinct functions: `awaken_deferred` (which resolves the given promise later) and `awaken_nested` (which resolves the promise now, and comes back to current code...
proposal: make two distinct functions instead of one with parameter `awaken_deferred`: awakens the promise the next time the scheduler kicks in (equivalent to doing `Lwt.on_success (Lwt.pause ()) (Lwt.wakeup …)` rn)...
Currently unhappy with the interface (the named parameter + constructor is too long). Alternatives: - separate functions? (also makes it easier to have `Lwt.t` in the return type of the...
An issue with delaying the resolution of the promise is that the double-wakening exception has no place to be raised at. It happens asyncly meaning it should be handled by...