We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, some features depend on std, such as the re-exporting of num_trait's Float (from here):
num_trait
Float
#[cfg(feature = "std")] pub use num_traits::{Float, Pow};
However, num_trait has the ability to export these using libm even under no_std (from here):
libm
no_std
#[cfg(any(feature = "std", feature = "libm"))] pub trait Float: Num + Copy + NumCast + PartialOrd + Neg<Output = Self> { ...
I think that it would be good for ordered-float to do the same, enabling a wider use of its feature set under no_std.
ordered-float
Does the maintainer agree?
The text was updated successfully, but these errors were encountered:
14c9153
Woah that was fast, thank you very much! :-)
Sorry, something went wrong.
Fyi I document this addition in #165.
No branches or pull requests
Currently, some features depend on std, such as the re-exporting of
num_trait
'sFloat
(from here):However,
num_trait
has the ability to export these usinglibm
even underno_std
(from here):I think that it would be good for
ordered-float
to do the same, enabling a wider use of its feature set underno_std
.Does the maintainer agree?
The text was updated successfully, but these errors were encountered: