Skip to content
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

Closed
nox opened this issue Jun 9, 2017 · 17 comments
Closed

Yank num 0.1.38 #297

nox opened this issue Jun 9, 2017 · 17 comments

Comments

@nox
Copy link

nox commented Jun 9, 2017

Feature-gating Float is a breaking change and should be done in 0.2.

servo/euclid#210

@CryZe
Copy link

CryZe commented Jun 9, 2017

Yep, my code isn't compiling anymore either (it's num-rational 0.1.37 that's not compiling though)

@nox
Copy link
Author

nox commented Jun 9, 2017

@CryZe Yeah, I said num only because this project seems to bump all crates at once, not just the one that needs a bump.

@LaylBongers
Copy link

Same here, I think this is happening for all crates using the image crate

@icefoxen
Copy link

icefoxen commented Jun 9, 2017

It's certainly happening for me.

@nox
Copy link
Author

nox commented Jun 9, 2017

Meanwhile, people can continue building their stuff with:

cargo update -p <culprit num crate> --precise 0.1.37

@cuviper
Copy link
Member

cuviper commented Jun 9, 2017

Sorry for the trouble! I have yanked both the new num and num-traits.

If I understand correctly, feature-gating any existing API is a breaking change to anyone currently using no-default-features. Which means we can't have no_std here without bumping semver.

cc #216 @vks

@cuviper
Copy link
Member

cuviper commented Jun 9, 2017

@CryZe It's not clear to me why num-rational would be broken though. Do I need to yank that too?

@CryZe
Copy link

CryZe commented Jun 9, 2017

I'm rebuilding the commit now, I'll tell you once it's done.

@cuviper
Copy link
Member

cuviper commented Jun 9, 2017

@nox

this project seems to bump all crates at once, not just the one that needs a bump.

FWIW, I do that for num since it re-exports everything. If people want some new functionality through the top-level crate, they need a version bump they can specify for their requirements.

@CryZe
Copy link

CryZe commented Jun 9, 2017

Yeah, that needs to be yanked too. I can't tell you why though.

@nox
Copy link
Author

nox commented Jun 9, 2017

FWIW, I do that for num since it re-exports everything. If people want some new functionality through the top-level crate, they need a version bump they can specify for their requirements.

Cargo always select the newest versions, so they would get the new functionality anyways. But I see your point.

@cuviper
Copy link
Member

cuviper commented Jun 9, 2017

😞 OK, num-rational 0.1.37 is yanked too.

@CryZe
Copy link

CryZe commented Jun 9, 2017

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.

@cuviper
Copy link
Member

cuviper commented Jun 9, 2017

@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.

homu added a commit that referenced this issue Jun 9, 2017
Revert "Auto merge of #296 - vks:no_std, r=cuviper"

This reverts commit 8b5d4ac, reversing
changes made to ef752e4.

See #297 -- it's a breaking change to feature-gate existing APIs.
@cuviper
Copy link
Member

cuviper commented Jun 9, 2017

New versions are published, reverting traits no_std and fixing rational without bigint.
Let me know if there's anything else!

@cuviper cuviper closed this as completed Jun 9, 2017
@CryZe
Copy link

CryZe commented Jun 9, 2017

The new crates seem to work, for me at least :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants