Conversation
- Use [u8; 1024] for now - Better error reporting when socket not found - Use correct vt6 path (changed when vt6tokio was introduced)
Open
laerling
force-pushed
the
connections_synchronous
branch
from
d230864 to
a75f0bf
Compare
laerling
force-pushed
the
connections_synchronous
branch
from
09817a8 to
3c91681
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.
Like stated in #2, we don't need asynchronous messaging for now.
Though, there are still a few todos for synchronous messaging:
[u8]instead of[u8; 1024]core.pub, handle it before the originally expected message