-
Notifications
You must be signed in to change notification settings - Fork 148
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
Yank num 0.1.38 #297
Comments
Yep, my code isn't compiling anymore either (it's num-rational 0.1.37 that's not compiling though) |
@CryZe Yeah, I said |
Same here, I think this is happening for all crates using the image crate |
It's certainly happening for me. |
Meanwhile, people can continue building their stuff with:
|
@CryZe It's not clear to me why num-rational would be broken though. Do I need to yank that too? |
I'm rebuilding the commit now, I'll tell you once it's done. |
FWIW, I do that for |
Yeah, that needs to be yanked too. I can't tell you why though. |
Cargo always select the newest versions, so they would get the new functionality anyways. But I see your point. |
😞 OK, num-rational 0.1.37 is yanked too. |
I figured out why. Ratio::from_float is used outside of the num-bigint feature gate in line 681 and 685, but Ratio::from_float only exists with the feature. |
@CryZe aha, thanks! We need even more CI feature testing then, as the script doesn't currently check individual crates with no-default. I'll work on that one. |
New versions are published, reverting traits no_std and fixing rational without bigint. |
The new crates seem to work, for me at least :D |
Feature-gating
Float
is a breaking change and should be done in 0.2.servo/euclid#210
The text was updated successfully, but these errors were encountered: