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

Shouldn't the "use of unstable library feature" error have an error number? #47397

Closed
carols10cents opened this issue Jan 12, 2018 · 1 comment
Assignees
Labels
A-diagnostics Area: Messages for errors, warnings, and lints

Comments

@carols10cents
Copy link
Member

I thought every error was supposed to have a number that one could look up in the error index, run rustc --explain with, etc... but if I run this code with stable rust 1.23.0:

fn testl() {
    ::std::u128::MAX;
}

I get:

error: use of unstable library feature 'i128' (see issue #35118)
 --> src/lib.rs:2:5
  |
2 |     ::std::u128::MAX;
  |     ^^^^^^^^^^^^^^^^

Rather than error[E0644] or something.

Feel free to close if this was a deliberate decision.

@carols10cents carols10cents added the A-diagnostics Area: Messages for errors, warnings, and lints label Jan 12, 2018
@GuillaumeGomez
Copy link
Member

Every error should have an error number! I'm adding it.

@GuillaumeGomez GuillaumeGomez self-assigned this Jan 13, 2018
GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this issue Jan 14, 2018
… r=estebank

Add error code for unstable feature errors

Fixes rust-lang#47397.
bors added a commit that referenced this issue Jan 15, 2018
Add error code for unstable feature errors

Fixes #47397.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-diagnostics Area: Messages for errors, warnings, and lints
Projects
None yet
Development

No branches or pull requests

2 participants