You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no issue #0 :-) I'm guessing someone intended #0 to mean "we don't have an issue for this", but either the error message emitting machinery needs to suppress it, or it should be given a real error message. Here's what it looks like:
error[E0658]: use of unstable library feature 'unicode_internals' (see issue #0)
--> /home/travis/.cargo/registry/src/git.colasdn.top-1ecc6299db9ec823/rustc-ap-syntax-94.0.0/parse/lexer/mod.rs:18:5
|
18 | use std_unicode::property::Pattern_White_Space;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= help: add #![feature(unicode_internals)] to the crate attributes to enable
error[E0658]: use of unstable library feature 'unicode_internals' (see issue #0)
--> /home/travis/.cargo/registry/src/git.colasdn.top-1ecc6299db9ec823/rustc-ap-syntax-94.0.0/parse/lexer/mod.rs:1725:21
|
1725 | c.map_or(false, Pattern_White_Space)
| ^^^^^^^^^^^^^^^^^^^
|
= help: add #![feature(unicode_internals)] to the crate attributes to enable
error: aborting due to 2 previous errors
The unstable-feature attribute requires an issue (neglecting it is
E0547), which gets used in the error messages. Unfortunately, there are
some cases where "0" is apparently used a placeholder where no issue
exists, directing the user to see the (nonexistent) issue #0. (It would
have been better to either let `issue` be optional—compare to how issue
is an `Option<u32>` in the feature-gate declarations in
libsyntax/feature-gate.rs—or actually require that an issue be created.)
Rather than endeavoring to change how `#[unstable]` works at this time
(given competing contributor and reviewer priorities), this simple patch
proposes the less-ambitious solution of just not adding the "(see
issue)" note when the number is zero.
Resolvesrust-lang#49983.
don't see issue #0
The unstable-feature attribute requires an issue (neglecting it is
E0547), which gets used in the error messages. Unfortunately, there are
some cases where "0" is apparently used a placeholder where no issue
exists, directing the user to see the (nonexistent) issue #0. (It would
have been better to either let `issue` be optional—compare to how issue
is an `Option<u32>` in the feature-gate declarations in
libsyntax/feature-gate.rs—or actually require that an issue be created.)
Rather than endeavoring to change how `#[unstable]` works at this time
(given competing contributor and reviewer priorities), this simple patch
proposes the less-ambitious solution of just not adding the "(see
issue)" note when the number is zero.
Resolvesrust-lang#49983.
There is no issue #0 :-) I'm guessing someone intended #0 to mean "we don't have an issue for this", but either the error message emitting machinery needs to suppress it, or it should be given a real error message. Here's what it looks like:
You can see it here: https://travis-ci.org/alex/ct-tools/builds/366818424
The text was updated successfully, but these errors were encountered: