-
Notifications
You must be signed in to change notification settings - Fork 16
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 for standalone crates
#313
Comments
This issue has been marked as stale due to a lack of activity for 60 days. If you believe this issue is still relevant, please provide an update or comment to keep it open. Otherwise, it will be closed in 7 days. |
@jschneider-bensch let's list the crates and what needs to get done. |
This issue has been marked as stale due to a lack of activity for 60 days. If you believe this issue is still relevant, please provide an update or comment to keep it open. Otherwise, it will be closed in 7 days. |
I made most crates no_std in #697. Some didn't work, though:
The PSQ one might be solvable, but I think our chances for sys/hacl are not very good. But since we are already in the way to migrating to hacl-rs, that is temporary. @franziskuskiefer if you don't have objections, I would close this as resolved. |
As you say, since this is for wrapping C code we don't care for the pure Rust version.
Let's not put this in scope for the first pure Rust release and file a separate issue for time not being in core.
Right, this is fine. Let's file that psq issue and close this. |
E.g. for
libcrux-kem
, or in general where possible.The text was updated successfully, but these errors were encountered: