Nuke libmultiprocess#44
Draft
josibake wants to merge 3 commits into
Draft
Conversation
josibake
force-pushed
the
nuke-libmultiprocess
branch
3 times, most recently
from
a738461 to
7afef92
Compare
josibake
force-pushed
the
nuke-libmultiprocess
branch
from
7afef92 to
70e3c06
Compare
josibake
force-pushed
the
nuke-libmultiprocess
branch
from
70e3c06 to
077a323
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is based on what I did in https://github.com/josibake/champy and is an attempt to not only take out libmultiprocess, but make Capnp a more idiomatic implementation. Currently only based on the mining interface, and there are some deeper cleanups that would make this even more pure async, but I think its too invasive at this stage.