A prototype inclusion of effect handling into the Lwt_main.run function
#961
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(I removed luv temporarily to make it easier to build and such)
|
This is an experimental branch. Closing the PR. Anyone interested in these experiments, feel free to ping me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using two schedulers at the same time doesn't really work. Even when they're not really schedulers! And so it's unsurprising that effects and Lwt don't mix well. See this experiment for an example of where it breaks down.
This PR is a prototype to allow users to pass an effect handler to the
Lwt_main.runfunction which in turn installs it around the appropriate calls.