-
Notifications
You must be signed in to change notification settings - Fork 4
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
[Discussion] no_std support #12
Comments
hello @SimonIT , thanks for the effort in adding no_std support to the crate. I believe you are adding this so that you can use the output of the The please have a look at the following: #14 This way the array and bytes data are completely left to the user of the crates and we don't need the BufRead dependency. What do you think? |
Good idea. Another problem I came across is the error handling:
|
if we go the path I'm suggesting we don't need |
We think everything is resolved. Our PR is working. Feel free to make some suggestions there #13 . |
Hey @NicolasDP,
@connectety and I want to use cddl-codegen with constrained devices.
For this, we need
no_std
compatibility.We started making the changes in our fork.
It seems that everything is compatible with
no_std
exceptBufRead
.For
BufRead
exists a drop-in replacement called acid_io.So I want to get some opinions from you maintainers about this.
Especially because of your statement:
The text was updated successfully, but these errors were encountered: