Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upno_std support? #189
no_std support? #189
Comments
|
Yes! I don't know what the biggest barriers are but we would love a PR to support no_std. |
|
A rough design could be:
Theoretically I hope that's it! Not a small amount of work, but hopefully doable |
|
I'm going to try and give this a shot this week |
|
It looks like we depend on rust-num/num#296, which is an open PR that will hopefully be done soonish! |
|
rust-num/num#296 has been merged, num-traits 0.1.38 can be build without std. |
|
I took an initial stab at this and it is way more difficult than I first anticipated. Also, ssmarshall does pretty much everything I needed https://crates.io/crates/ssmarshal Not sure where this issue should go, but I won't be working on it! |
|
Thus crate could be no_std, but it would basically be ssmarshall with u32 enum variants and configurable byte ordering |
|
Yeah... bincode is pretty dependent on |
|
core_io's documentation says that it provides the Read and Write traits for use with |
|
Take a look on my crate tirse. I just committed, the work still in progress. |
|
Any update on this? |
|
I think no_std support is not intended for bincode. Such support would likely require significant limitations, see the ssmarshall crate, which is essentially a reimagination of bincode for no_std applications. |
|
The no_std story has really changed since 2 years ago. It's a lot easier to provide no_std support nowadays. |
|
some context: there IS a protobuf implementation (in C) for micro-controllers: |
I didn't see no_std support in the documentation / cargo.toml / issues so I thought I would open one. This library seems perfect for no_std serialization in microcontrollers. What are the biggest barriers to supporting no_std? Would you welcome a PR that did so?
Thanks!