rust/tests/ui/consts/const-eval/stable-metric/ctfe-labelled-loop.stderr

error: constant evaluation is taking a long time
  --> $DIR/ctfe-labelled-loop.rs:6:5
   |
LL | /     'mylabel: loop {
LL | |
LL | |         if i > n {
LL | |             break 'mylabel;
LL | |         }
LL | |         i += 1;
LL | |     }
   | |_____^
   |
   = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
           If your compilation actually takes a long time, you can safely allow the lint.
help: the constant being evaluated
  --> $DIR/ctfe-labelled-loop.rs:16:1
   |
LL | const X: u32 = labelled_loop(19);
   | ^^^^^^^^^^^^
   = note: `#[deny(long_running_const_eval)]` on by default

error: aborting due to 1 previous error
Remove const eval limit and implement an exponential backoff lint instead 2022-11-02 06:57:40 -05:00			`error: constant evaluation is taking a long time`
Replace terminator-based const eval limit - Remove logic that limits const eval based on terminators, and use the stable metric instead (back edges + fn calls) - Add unstable flag `tiny-const-eval-limit` to add UI tests that do not have to go up to the regular 2M step limit 2022-12-29 17:14:29 -06:00			`--> $DIR/ctfe-labelled-loop.rs:6:5`
			`\|`
			`LL \| / 'mylabel: loop {`
Remove const eval limit and implement an exponential backoff lint instead 2022-11-02 06:57:40 -05:00			`LL \| \|`
Replace terminator-based const eval limit - Remove logic that limits const eval based on terminators, and use the stable metric instead (back edges + fn calls) - Add unstable flag `tiny-const-eval-limit` to add UI tests that do not have to go up to the regular 2M step limit 2022-12-29 17:14:29 -06:00			`LL \| \| if i > n {`
Remove const eval limit and implement an exponential backoff lint instead 2022-11-02 06:57:40 -05:00			`LL \| \| break 'mylabel;`
Replace terminator-based const eval limit - Remove logic that limits const eval based on terminators, and use the stable metric instead (back edges + fn calls) - Add unstable flag `tiny-const-eval-limit` to add UI tests that do not have to go up to the regular 2M step limit 2022-12-29 17:14:29 -06:00			`LL \| \| }`
			`LL \| \| i += 1;`
			`LL \| \| }`
			`\| \|_____^`
Remove const eval limit and implement an exponential backoff lint instead 2022-11-02 06:57:40 -05:00			`\|`
			`= note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.`
			`If your compilation actually takes a long time, you can safely allow the lint.`
			`help: the constant being evaluated`
			`--> $DIR/ctfe-labelled-loop.rs:16:1`
Replace terminator-based const eval limit - Remove logic that limits const eval based on terminators, and use the stable metric instead (back edges + fn calls) - Add unstable flag `tiny-const-eval-limit` to add UI tests that do not have to go up to the regular 2M step limit 2022-12-29 17:14:29 -06:00			`\|`
			`LL \| const X: u32 = labelled_loop(19);`
Remove const eval limit and implement an exponential backoff lint instead 2022-11-02 06:57:40 -05:00			`\| ^^^^^^^^^^^^`
			= note: `#[deny(long_running_const_eval)]` on by default
Create stable metric to measure long computation in Const Eval This patch adds a `MirPass` that tracks the number of back-edges and function calls in the CFG, adds a new MIR instruction to increment a counter every time they are encountered during Const Eval, and emit a warning if a configured limit is breached. 2022-12-19 18:51:17 -06:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Create stable metric to measure long computation in Const Eval This patch adds a `MirPass` that tracks the number of back-edges and function calls in the CFG, adds a new MIR instruction to increment a counter every time they are encountered during Const Eval, and emit a warning if a configured limit is breached. 2022-12-19 18:51:17 -06:00