-
I think the generated code can easily be `#![no_std]`. We only _need_ `std` to `impl std::error::Error for rinja::Error`. We _need_ `alloc` for a few filters. Both use cases can be feature-gated. Then…
-
It seems that the dependencies of this crate all support no_std. It seems that it is possible for this crate to support no_std. Is there any hidden problem? If it is possible, I can try to complete it…
-
error[E0405]: cannot find trait `Sync` in this scope
--> /home/esp/.cargo/registry/src/index.crates.io-6f17d22bba150
01f/thiserror-1.0.61/src/aserror.rs:50:40
|
50 | ...ror + Send + Sync + Un…
-
Is it possible to go `no_std` like `async-channel`? I am planning to use this crate on an esp32 (no_std + allocator)
I have already a bittried, but I had some problems getting it up and running no_…
dscso updated
2 months ago
-
### Describe the feature
Ideally, we want to have a subset of crates with no_std supports (evm specifically)
```[tasklist]
- [x] storage-errors https://github.com/paradigmxyz/reth/issues/8459
…
-
It'd be great if I could use the `rquickjs` crate on no_std targets as an embedded JavaScript engine.
-
It would probably be very valuable if some method could be developed that allows for true testing of actual `#![no_std]` Rust objects, even if it requires some additional work to set up, special harne…
-
```
error: Wasmtime is being compiled for an architecture that it does not support. If this architecture is one you would like to see supported you may file an issue on Wasmtime's issue tracker: http…
-
This is an issue to propose the idea of considering adding `no_std` support. `include_str!` and `include_bytes!` both have it, so it would make sense for this too.
jlxip updated
2 weeks ago
-
Would you be interested in patches to make the `url` library support a `no_std` build configuration based on the alloc crate instead? I think it should be possible and will make the library more easil…