android: switch from futures-channel to async-channel. #12
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
`futures-channel` doesn't support blocking send, so in the callbacks from java (which are not in an async context) we're forced to do `try_send`, which will lose data if the channel is full because the Rust side is too busy. This is not a big deal for scanning, but is for stuff like gatt/l2cap responses that are coming next.
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.
futures-channeldoesn't support blocking send, so in the callbacks from java(which are not in an async context) we're forced to do
try_send, which will losedata if the channel is full because the Rust side is too busy.
This is not a big deal for scanning, but is for stuff like gatt/l2cap responses that
are coming next.