Skip to content

Stability: tweak rules for trait impls #19969

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

Merged
merged 1 commit into from
Dec 22, 2014

Conversation

aturon
Copy link
Member

@aturon aturon commented Dec 18, 2014

There is currently no way to specify the stability level for a trait
impl produced by deriving. This patch is a stopgap solution that:

  • Turns of stability inheritance for trait impls, and
  • Uses the stability level of the trait if no level is directly
    specified.

That is, manual trait impls may still provide a directly stability
level, but deriving will use the level of the trait. While not a
perfect solution, it should be good enough for 1.0 API stabilization, as
we will like remove any unwanted impls outright.

r? @alexcrichton

There is currently no way to specify the stability level for a trait
impl produced by `deriving`. This patch is a stopgap solution that:

* Turns of stability inheritance for trait impls, and
* Uses the stability level of the *trait* if no level is directly
  specified.

That is, manual trait impls may still provide a directly stability
level, but `deriving` will use the level of the trait. While not a
perfect solution, it should be good enough for 1.0 API stabilization, as
we will like *remove* any unwanted impls outright.
alexcrichton added a commit to alexcrichton/rust that referenced this pull request Dec 21, 2014
There is currently no way to specify the stability level for a trait
impl produced by `deriving`. This patch is a stopgap solution that:

* Turns of stability inheritance for trait impls, and
* Uses the stability level of the *trait* if no level is directly
  specified.

That is, manual trait impls may still provide a directly stability
level, but `deriving` will use the level of the trait. While not a
perfect solution, it should be good enough for 1.0 API stabilization, as
we will like *remove* any unwanted impls outright.

r? @alexcrichton
@bors bors merged commit 9bb5380 into rust-lang:master Dec 22, 2014
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

Successfully merging this pull request may close these issues.

3 participants