rust/tests/ui/feature-gates/issue-49983-see-issue-0.stderr

error[E0658]: use of unstable library feature 'ptr_internals': use `NonNull` instead and consider `PhantomData<T>` (if you also use `#[may_dangle]`), `Send`, and/or `Sync`
  --> $DIR/issue-49983-see-issue-0.rs:4:30
   |
LL | #[allow(unused_imports)] use core::ptr::Unique;
   |                              ^^^^^^^^^^^^^^^^^
   |
   = help: add `#![feature(ptr_internals)]` to the crate attributes to enable
   = note: this compiler was built on YYYY-MM-DD; consider upgrading it if it is out of date

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0658`.
normalize use of backticks in compiler messages for libcore/ptr https://github.com/rust-lang/rust/issues/60532 2019-07-18 20:32:24 +00:00			error[E0658]: use of unstable library feature 'ptr_internals': use `NonNull` instead and consider `PhantomData<T>` (if you also use `#[may_dangle]`), `Send`, and/or `Sync`
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/issue-49983-see-issue-0.rs:4:30`
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. Resolves #49983. 2018-04-15 18:12:33 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| #[allow(unused_imports)] use core::ptr::Unique;`
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. Resolves #49983. 2018-04-15 18:12:33 +00:00			`\| ^^^^^^^^^^^^^^^^^`
			`\|`
normalize use of backticks in compiler messages for libsyntax/feature_gate https://github.com/rust-lang/rust/issues/60532 2019-07-09 09:32:08 +00:00			= help: add `#![feature(ptr_internals)]` to the crate attributes to enable
Bless tests Update tests 2024-01-10 06:39:02 +00:00			`= note: this compiler was built on YYYY-MM-DD; consider upgrading it if it is out of date`
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. Resolves #49983. 2018-04-15 18:12:33 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
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. Resolves #49983. 2018-04-15 18:12:33 +00:00
			For more information about this error, try `rustc --explain E0658`.