rust/tests/ui/macros/issue-16098.stderr

error: recursion limit reached while expanding `prob1!`
  --> $DIR/issue-16098.rs:7:18
   |
LL |             $n + prob1!($n - 1);
   |                  ^^^^^^^^^^^^^^
...
LL |     println!("Problem 1: {}", prob1!(1000));
   |                               ------------ in this macro invocation
   |
   = help: consider increasing the recursion limit by adding a `#![recursion_limit = "256"]` attribute to your crate (`issue_16098`)
   = note: this error originates in the macro `prob1` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error
rustc_span: move pretty syntax from macro_backtrace to ExpnKind::descr. 2020-01-20 17:02:01 -06:00			error: recursion limit reached while expanding `prob1!`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-16098.rs:7:18`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| $n + prob1!($n - 1);`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\| ^^^^^^^^^^^^^^`
			`...`
			`LL \| println!("Problem 1: {}", prob1!(1000));`
			`\| ------------ in this macro invocation`
			`\|`
Improve help for recursion limit errors 2021-09-28 15:16:42 -05:00			= help: consider increasing the recursion limit by adding a `#![recursion_limit = "256"]` attribute to your crate (`issue_16098`)
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 13:52:25 -06:00			= note: this error originates in the macro `prob1` (in Nightly builds, run with -Z macro-backtrace for more info)
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00
			`error: aborting due to previous error`