rust/tests/ui/feature-gates/feature-gate-log_syntax2.stderr

error[E0658]: use of unstable library feature `log_syntax`: `log_syntax!` is not stable enough for use and is subject to change
  --> $DIR/feature-gate-log_syntax2.rs:2:22
   |
LL |     println!("{:?}", log_syntax!());
   |                      ^^^^^^^^^^
   |
   = note: see issue #29598 <https://github.com/rust-lang/rust/issues/29598> for more information
   = help: add `#![feature(log_syntax)]` 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`.
use backticks instead of single quotes when reporting "use of unstable library feature" This is consistent with all other diagnostics I could find containing features and enables the use of `DiagSymbolList` for generalizing diagnostics for unstable library features to multiple features. 2024-11-02 18:10:24 -05:00			error[E0658]: use of unstable library feature `log_syntax`: `log_syntax!` is not stable enough for use and is subject to change
cleanup: Remove some language features related to built-in macros They are now library features. 2019-07-28 06:02:08 -05:00			`--> $DIR/feature-gate-log_syntax2.rs:2:22`
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common. 2017-12-06 03:18:03 -06:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| println!("{:?}", log_syntax!());`
resolve: Divide macro path resolution into speculative and error reporting parts Also move macro stability checking closer to other checks performed on obtained resolutions. Tighten the stability spans as well, it is an error to refer to and unstable entity in any way, not only "call" it. 2019-07-03 15:59:03 -05:00			`\| ^^^^^^^^^^`
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common. 2017-12-06 03:18:03 -06:00			`\|`
--bless --compare-mode=nll 2020-02-07 06:07:02 -06:00			`= note: see issue #29598 <https://github.com/rust-lang/rust/issues/29598> for more information`
normalize use of backticks in compiler messages for libsyntax/feature_gate https://github.com/rust-lang/rust/issues/60532 2019-07-09 04:32:08 -05:00			= help: add `#![feature(log_syntax)]` to the crate attributes to enable
Bless tests Update tests 2024-01-10 00:39:02 -06:00			`= note: this compiler was built on YYYY-MM-DD; consider upgrading it if it is out of date`
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common. 2017-12-06 03:18:03 -06:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common. 2017-12-06 03:18:03 -06:00
update tests 2018-03-03 08:59:40 -06:00			For more information about this error, try `rustc --explain E0658`.