nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2025-04-29 19:47:38 +00:00
Code Issues Packages Projects Releases Wiki Activity
4b65a86eba
rust/src/test/ui/macros/format-parse-errors.stderr

51 lines
1.4 KiB
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: requires at least a format string argument
--> $DIR/format-parse-errors.rs:2:5
|
Update tests
2019-03-09 12:03:44 +00:00
LL | format!();
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
| ^^^^^^^^^^
|
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
error: expected expression, found keyword `struct`
--> $DIR/format-parse-errors.rs:3:13
|
Update tests
2019-03-09 12:03:44 +00:00
LL | format!(struct);
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 expression
Tweak macro parse errors when reaching EOF during macro call parse - Add detail on origin of current parser when reaching EOF and stop saying "found <eof>" and point at the end of macro calls - Handle empty `cfg_attr` attribute - Reword empty `derive` attribute error
2019-05-22 00:47:23 +00:00
error: expected expression, found end of macro arguments
--> $DIR/format-parse-errors.rs:4:24
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
|
Update tests
2019-03-09 12:03:44 +00:00
LL | format!("s", name =);
Tweak macro parse errors when reaching EOF during macro call parse - Add detail on origin of current parser when reaching EOF and stop saying "found <eof>" and point at the end of macro calls - Handle empty `cfg_attr` attribute - Reword empty `derive` attribute error
2019-05-22 00:47:23 +00:00
| ^ expected expression
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
Tweak macro parse errors when reaching EOF during macro call parse - Add detail on origin of current parser when reaching EOF and stop saying "found <eof>" and point at the end of macro calls - Handle empty `cfg_attr` attribute - Reword empty `derive` attribute error
2019-05-22 00:47:23 +00:00
error: expected `=`, found end of macro arguments
--> $DIR/format-parse-errors.rs:5:32
don't unwrap unexpected tokens in `format!` Fixes #57512.
2019-01-11 17:40:05 +00:00
|
Update tests
2019-03-09 12:03:44 +00:00
LL | format!("s", foo = foo, bar);
Tweak macro parse errors when reaching EOF during macro call parse - Add detail on origin of current parser when reaching EOF and stop saying "found <eof>" and point at the end of macro calls - Handle empty `cfg_attr` attribute - Reword empty `derive` attribute error
2019-05-22 00:47:23 +00:00
| ^ expected `=`
don't unwrap unexpected tokens in `format!` Fixes #57512.
2019-01-11 17:40:05 +00:00
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 expression, found keyword `struct`
don't unwrap unexpected tokens in `format!` Fixes #57512.
2019-01-11 17:40:05 +00:00
--> $DIR/format-parse-errors.rs:6:24
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
|
Update tests
2019-03-09 12:03:44 +00:00
LL | format!("s", foo = struct);
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 expression
error: expected expression, found keyword `struct`
don't unwrap unexpected tokens in `format!` Fixes #57512.
2019-01-11 17:40:05 +00:00
--> $DIR/format-parse-errors.rs:7:18
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
|
Update tests
2019-03-09 12:03:44 +00:00
LL | format!("s", struct);
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 expression
error: format argument must be a string literal
don't unwrap unexpected tokens in `format!` Fixes #57512.
2019-01-11 17:40:05 +00:00
--> $DIR/format-parse-errors.rs:10:13
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
|
Update tests
2019-03-09 12:03:44 +00:00
LL | format!(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
| ^^^
help: you might be missing a string literal to format with
|
Update tests
2019-03-09 12:03:44 +00:00
LL | format!("{}", 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
| ^^^^^
don't unwrap unexpected tokens in `format!` Fixes #57512.
2019-01-11 17:40:05 +00:00
error: aborting due to 7 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
Reference in New Issue Copy Permalink