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

Prepare to breaking changes #261

Closed
hauleth opened this issue Feb 3, 2017 · 3 comments
Closed

Prepare to breaking changes #261

hauleth opened this issue Feb 3, 2017 · 3 comments

Comments

@hauleth
Copy link
Member

hauleth commented Feb 3, 2017

I think that as we got custom derive support in stable we should think about freezing 0.1.x branch and think about jump to 0.2 with breaking changes.

cc @cuviper

@cuviper
Copy link
Member

cuviper commented Feb 3, 2017

Did you see #257? I think due to that break out of our control, we could go ahead and raise our base to Rust 1.8 without breaking things any further, and thus get access to some nice things like OpAssign traits.

If we want custom derive, we have to jump all the way to 1.15. Maybe that's justifiable, but I'm also looking towards i128/u128 stabilizing sometime soon, and that's a much stronger fit for num. However, that might also be possible to just add behind a simple num128 feature.

We can still stabilize num-derive on 1.15+ regardless, as that was nightly-only until now.

@cuviper
Copy link
Member

cuviper commented Jun 9, 2017

I've opened a next branch and #302 to start it.

@cuviper
Copy link
Member

cuviper commented Dec 19, 2017

Semver bumps should now be considered on each crate's separate repo.

cc #354 #356

@cuviper cuviper closed this as completed Dec 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants