rust/tests/ui/macros/assert.without-generic-asse...

error: macro requires a boolean expression as an argument
  --> $DIR/assert.rs:5:5
   |
LL |     assert!();
   |     ^^^^^^^^^ boolean expression required

error: expected expression, found keyword `struct`
  --> $DIR/assert.rs:6:13
   |
LL |     assert!(struct);
   |             ^^^^^^ expected expression

error: macro requires a boolean expression as an argument
  --> $DIR/assert.rs:7:5
   |
LL |     debug_assert!();
   |     ^^^^^^^^^^^^^^^ boolean expression required
   |
   = note: this error originates in the macro `debug_assert` (in Nightly builds, run with -Z macro-backtrace for more info)

error: expected expression, found keyword `struct`
  --> $DIR/assert.rs:8:19
   |
LL |     debug_assert!(struct);
   |                   ^^^^^^ expected expression

error: aborting due to 4 previous errors
emit error with span for empty asserts Fixes #55547. 2018-12-04 09:45:25 +08:00			`error: macro requires a boolean expression as an argument`
[RFC 2011] Minimal initial implementation 2022-06-15 18:37:40 +08:00			`--> $DIR/assert.rs:5:5`
emit error with span for empty asserts Fixes #55547. 2018-12-04 09:45:25 +08:00			`\|`
Update tests 2019-03-09 20:03:44 +08:00			`LL \| assert!();`
Bless tests 2021-10-15 02:28:28 +08:00			`\| ^^^^^^^^^ boolean expression required`
emit error with span for empty asserts Fixes #55547. 2018-12-04 09:45:25 +08: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-05 03:10:32 +08:00			error: expected expression, found keyword `struct`
[RFC 2011] Minimal initial implementation 2022-06-15 18:37:40 +08:00			`--> $DIR/assert.rs:6: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-05 03:10:32 +08:00			`\|`
Update tests 2019-03-09 20:03:44 +08:00			`LL \| assert!(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-05 03:10:32 +08:00			`\| ^^^^^^ expected expression`

emit error with span for empty asserts Fixes #55547. 2018-12-04 09:45:25 +08:00			`error: macro requires a boolean expression as an argument`
[RFC 2011] Minimal initial implementation 2022-06-15 18:37:40 +08:00			`--> $DIR/assert.rs:7:5`
emit error with span for empty asserts Fixes #55547. 2018-12-04 09:45:25 +08:00			`\|`
Update tests 2019-03-09 20:03:44 +08:00			`LL \| debug_assert!();`
Bless tests 2021-10-15 02:28:28 +08:00			`\| ^^^^^^^^^^^^^^^ boolean expression required`
emit error with span for empty asserts Fixes #55547. 2018-12-04 09:45:25 +08: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-14 03:52:25 +08:00			= note: this error originates in the macro `debug_assert` (in Nightly builds, run with -Z macro-backtrace for more info)
emit error with span for empty asserts Fixes #55547. 2018-12-04 09:45:25 +08: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-05 03:10:32 +08:00			error: expected expression, found keyword `struct`
[RFC 2011] Minimal initial implementation 2022-06-15 18:37:40 +08:00			`--> $DIR/assert.rs:8:19`
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-05 03:10:32 +08:00			`\|`
Update tests 2019-03-09 20:03:44 +08:00			`LL \| debug_assert!(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-05 03:10:32 +08:00			`\| ^^^^^^ expected expression`

			`error: aborting due to 4 previous errors`
emit error with span for empty asserts Fixes #55547. 2018-12-04 09:45:25 +08:00