-
-
Notifications
You must be signed in to change notification settings - Fork 14
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 compatability #20
Comments
Hi, please use version |
How are you testing the core compatibility? When I build in no_std, I get errors because Would you accept a patch that includes optional linking to libm when std is disabled? |
Which rust version are you using? On my machine, I use
|
yeah, building by itself seems to work OK for some reason but you can't link it into a project. I've been able to make it fail locally using libm is definitely less desirable as it doesn't have access to the llvm intrisics that the standard library is using, but as far as I am aware it is the best portable option if you don't have access to intrinsics. If you're OK with making no_std available only to nightly, I can add the intrinsics back in as a feature since they're available in core behind a feature gate. EDIT: just a note that |
Since this ticket is still open: I'm on I tried the latest commit (bd2816c) since I've noticed the new version 0.2.9 which is not published yet, but even with adding
Is there anything I am missing? |
How do you get the crate to compile in no_std environments?
running
cargo check --no-default-features --features hashbrown
give the following error importingstd
:The text was updated successfully, but these errors were encountered: