Correctly map astro-float
features to astro-float-num
features
#34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adjusts the features in this crate to correctly map to features in the
astro-float-num
crate.The existing features for the
astro-float
crate don't actually enable/disable anything in theastro-float-num
crate becauseastro-float-num
is used as a dependency with default features. Thus, if a user defines a dependency onastro-float
withdefault-features = false
,astro-float-num
will still build with theserde
,random
, andstd
features.By defaulting the
astro-float-num
dependency todefault-features = false
, the use case mentioned above works as expected.