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

no_std compatibility #10

Open
archseer opened this issue Jan 25, 2019 · 0 comments
Open

no_std compatibility #10

archseer opened this issue Jan 25, 2019 · 0 comments
Labels
K-research This topic is still being researched

Comments

@archseer
Copy link
Owner

archseer commented Jan 25, 2019

We currently rely on some parts of std, but having a no_std build would be interesting for embedded devices and WebAssembly. Note that a lot of the std stuff exists in core, so we could get far with just conditional imports.

https://github.com/serde-rs/serde/blob/bb99b31eb0a55393101f9c80cd959b3a739ad70f/serde/src/lib.rs#L141-L143

  • Fix all the imports to import core:: + alloc versions on the no_std feature flag.
  • Make sure all the dependencies are no_std capable.
  • Move any OS specific code to a sys subfolder.
  • Abstract the tokio runtime so we can switch to juliex or any other no_std capable executor. Look into fuchsia's executor as an example.
@archseer archseer added the K-research This topic is still being researched label Jan 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
K-research This topic is still being researched
Projects
None yet
Development

No branches or pull requests

1 participant