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
{{ message }}
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.
Yep, this is a bug. Architecturally, rust-async-coap is designed to eventually allow for use in no_std mode without even alloc. However, getting things to work without alloc is going to require generic associated types to land, so I didn't bother too much with it other than to make sure that architecturally it wasn't precluded from being introduced later.
However, there is no good reason for not supporting no_std with alloc right now. Getting that implemented would be a good step toward reaching that eventual goal once GAT lands.
The crate provides the following features:
by default
std
is enabled, which works as expected.To test the features I simply ran the tests of
async-coap-uri
with the below commands.To disable all default features one could try the following command (this would be true
no_std
without any allocator):which fails (with lots of errors).
Enabling only the
alloc
-feature also failsThe text was updated successfully, but these errors were encountered: