nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-23 07:14:28 +00:00
Code Issues Packages Projects Releases Wiki Activity
3171c989ef
rust/tests/ui/macros/cfg.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

32 lines
860 B
Plaintext
Raw Normal View History

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!();
Bless tests
2021-10-14 18:28:28 +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
|
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
2021-02-13 19:52:25 +00:00
= note: this error originates in the macro `cfg` (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
| ^^^
Add UI test for `cfg!(foo, bar)`
2022-06-21 18:28:22 +00:00
error: expected 1 cfg-pattern
--> $DIR/cfg.rs:5:5
|
LL | cfg!(foo, bar);
| ^^^^^^^^^^^^^^
|
= note: this error originates in the macro `cfg` (in Nightly builds, run with -Z macro-backtrace for more info)
error: aborting due to 4 previous errors
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
For more information about this error, try `rustc --explain E0565`.
Reference in New Issue Copy Permalink