You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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 thatSerialStream
in this repo does not implementfutures::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
andSink
of bytes, in the fashion thatfutures_util
defines them?The text was updated successfully, but these errors were encountered: