Currently, some features depend on std, such as the re-exporting of num_trait's Float (from here):
#[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):
#[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.
Does the maintainer agree?
Currently, some features depend on std, such as the re-exporting of
num_trait'sFloat(from here):However,
num_traithas the ability to export these usinglibmeven underno_std(from here):I think that it would be good for
ordered-floatto do the same, enabling a wider use of its feature set underno_std.Does the maintainer agree?