rust/src/test/ui/macros/cfg.stderr

error: macro requires a cfg-pattern as an argument
  --> $DIR/cfg.rs:2:5
   |
LL |     cfg!();
   |     ^^^^^^^ cfg-pattern required
   |
   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error: expected identifier, found `123`
  --> $DIR/cfg.rs:3:10
   |
LL |     cfg!(123);
   |          ^^^ expected identifier

error[E0565]: literal in `cfg` predicate value must be a string
  --> $DIR/cfg.rs:4:16
   |
LL |     cfg!(foo = 123);
   |                ^^^

error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0565`.
make `panictry!` private to libsyntax This commit completely removes usage of the `panictry!` macro from outside libsyntax. The macro causes parse errors to be fatal, so using it in libsyntax_ext caused parse failures within a syntax extension to be fatal, which is probably not intended. Furthermore, this commit adds spans to diagnostics emitted by empty extensions if they were missing, à la #56491. 2018-12-04 19:10:32 +00:00			`error: macro requires a cfg-pattern as an argument`
			`--> $DIR/cfg.rs:2:5`
			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| cfg!();`
make `panictry!` private to libsyntax This commit completely removes usage of the `panictry!` macro from outside libsyntax. The macro causes parse errors to be fatal, so using it in libsyntax_ext caused parse failures within a syntax extension to be fatal, which is probably not intended. Furthermore, this commit adds spans to diagnostics emitted by empty extensions if they were missing, à la #56491. 2018-12-04 19:10:32 +00:00			`\| ^^^^^^^ cfg-pattern required`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 13:56:47 +00:00			`\|`
			`= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)`
make `panictry!` private to libsyntax This commit completely removes usage of the `panictry!` macro from outside libsyntax. The macro causes parse errors to be fatal, so using it in libsyntax_ext caused parse failures within a syntax extension to be fatal, which is probably not intended. Furthermore, this commit adds spans to diagnostics emitted by empty extensions if they were missing, à la #56491. 2018-12-04 19:10:32 +00:00
			error: expected identifier, found `123`
			`--> $DIR/cfg.rs:3:10`
			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| cfg!(123);`
make `panictry!` private to libsyntax This commit completely removes usage of the `panictry!` macro from outside libsyntax. The macro causes parse errors to be fatal, so using it in libsyntax_ext caused parse failures within a syntax extension to be fatal, which is probably not intended. Furthermore, this commit adds spans to diagnostics emitted by empty extensions if they were missing, à la #56491. 2018-12-04 19:10:32 +00:00			`\| ^^^ expected identifier`

			error[E0565]: literal in `cfg` predicate value must be a string
			`--> $DIR/cfg.rs:4:16`
			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| cfg!(foo = 123);`
make `panictry!` private to libsyntax This commit completely removes usage of the `panictry!` macro from outside libsyntax. The macro causes parse errors to be fatal, so using it in libsyntax_ext caused parse failures within a syntax extension to be fatal, which is probably not intended. Furthermore, this commit adds spans to diagnostics emitted by empty extensions if they were missing, à la #56491. 2018-12-04 19:10:32 +00:00			`\| ^^^`

			`error: aborting due to 3 previous errors`

			For more information about this error, try `rustc --explain E0565`.