-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate Lwt_main.yield and Lwt_unix.yield? #855
Comments
How do you yield then? 🤔 |
|
See Lines 45 to 52 in 9cbf3a9
and https://discuss.ocaml.org/t/lwt-pause-versus-yield/7875. |
See #784 for some earlier discussion of this. TL;DR:
I think that, before we release this we should:
Then if all of that goes well, we can release. It'll need a "breaking change" mention in the changelog. Maybe we could leverage the opam infrastructure to test if we break some of the tests of the opam packages. I think we should do this (if possible), make upstream commits to all possibly broken packages, and we should make a special mention of this in the changelog (and advertise it in advance on discuss too). |
I just updated |
I'll ask some opam wizards about the general test of all dependencies. |
... by replacing them with the almost-equivalent `Lwt.pause`. Promises constructed in this way have slightly different scheduling behaviour, but this shouldn't impact the correctness of our code. See ocsigen/lwt#855 for more details.
... by replacing them with the almost-equivalent `Lwt.pause`. Promises constructed in this way have slightly different scheduling behaviour, but this shouldn't impact the correctness of our code. See ocsigen/lwt#855 for more details. (cherry picked from commit 04a5bfa)
... by replacing them with the almost-equivalent `Lwt.pause`. Promises constructed in this way have slightly different scheduling behaviour, but this shouldn't impact the correctness of our code. See ocsigen/lwt#855 for more details. (cherry picked from commit 04a5bfa)
Closing this as #917 will complete every actionable items in this issue. |
This is a suggestion. After talking to @aantron on Discourse, I feel we should officially deprecate
yield
and related functions using[@@alert deprecate]
, in hope that one day we will merge the two pools into one.The text was updated successfully, but these errors were encountered: