Skip to content
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

How close is Source to a Stream<..some bytes type..>? #44

Open
akauppi opened this issue Apr 4, 2024 · 0 comments
Open

How close is Source to a Stream<..some bytes type..>? #44

akauppi opened this issue Apr 4, 2024 · 0 comments

Comments

@akauppi
Copy link

akauppi commented Apr 4, 2024

I'm trying to read and write a serial port using streaming, and would like to do it without Tokio dependencies.

mio-serial looks close, but I'm a newbie to Async Rust and cannot estimate "how close". Some observations:

  • Stream is not stable in Rust; I am aware of that
  • SerialStream in this repo does not implement futures::Stream. That is fine - things change and I am not complaining. Just that my initial expectation by the name was ... that it would. Silly me!

I am okey making some glue code in my own code. What I want is to implement the ASH protocol (Silicon Labs, PDF) in Rust. It's an async protocol for UART comms. Two messages can be "in flight" - very suitable for async/.await imho.

I noticed the code has Source but I am not sure what I can do with it.

How close is this to Stream and Sink of bytes, in the fashion that futures_util defines them?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant