Properly support no_std #312
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
emilio
reviewed
Jan 12, 2019
| @@ -72,6 +78,7 @@ where | |||
| } | |||
| } | |||
|
|
|||
| #[cfg(feature = "std")] | |||
There was a problem hiding this comment.
no trigonometry in FloatCore
|
☔ The latest upstream changes (presumably #314) made this pull request unmergeable. Please resolve the merge conflicts. |
|
@Manishearth other than rebasing, is there anything keeping us from going through with this? |
|
Rebasing and review |
|
Fixed in #372 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
num-traits isn't no-std by default, and we use a bunch of stuff from it that requires std
r? @SimonSapin
This change is