Skip to content

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

Closed
@carols10cents

Description

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

Activity

GuillaumeGomez

GuillaumeGomez commented on Jan 13, 2018

@GuillaumeGomez
Member

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

added a commit that references this issue on Jan 14, 2018

Rollup merge of rust-lang#47413 - GuillaumeGomez:unstable-error-code,…

841cd47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

A-diagnosticsArea: Messages for errors, warnings, and lints

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @carols10cents@GuillaumeGomez

      Issue actions

        Shouldn't the "use of unstable library feature" error have an error number? · Issue #47397 · rust-lang/rust