BurntSushi / BurntSushi/byteorder
Feature Request: Support for embedded-io
- Dominant language
- Rust
- Stars
- 1.1k
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
Hi, do you have any plan on supporting the [Read](https://github.com/rust-embedded/embedded-hal/blob/dd0bbbaa5c926628ff03dfd78fb54162fec05ab9/embedded-io/src/lib.rs#L304) and [Write](https://github.com/rust-embedded/embedded-hal/blob/dd0bbbaa5c926628ff03dfd78fb54162fec05ab9/embedded-io/src/lib.rs#L379) crates defined in [embedded-io](https://github.com/rust-embedded/embedded-hal/tree/master/embedded-io)?
It would be great to be able to use this library in embedded systems (where `std::io::Read` and `std::io::Write` are not available).
Thank you!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the linked embedded-io Read and Write traits and the byteorder library's current std::io integration. Determine the compatibility approach needed for embedded systems without std; done means byteorder can be used with those traits in no_std environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100