rust/tests/ui/treat-err-as-bug/span_delayed_bug.stderr

error: internal compiler error: delayed bug triggered by #[rustc_delayed_bug_from_inside_query]
  --> $DIR/span_delayed_bug.rs:12:1
   |
LL | fn main() {}
   | ^^^^^^^^^


error: the compiler unexpectedly panicked. this is a bug.

query stack during panic:
#0 [trigger_delayed_bug] triggering a delayed bug for testing incremental
end of query stack
Remove attribute `#[rustc_error]` 2025-03-30 00:39:55 +03:00			`error: internal compiler error: delayed bug triggered by #[rustc_delayed_bug_from_inside_query]`
Rename `HandlerInner::delay_span_bug` as `HandlerInner::span_delayed_bug`. Because the corresponding `Level` is `DelayedBug` and `span_delayed_bug` follows the pattern used everywhere else: `span_err`, `span_warning`, etc. 2023-11-30 15:01:11 +11:00			`--> $DIR/span_delayed_bug.rs:12:1`
Create ui test for -Ztreat-err-as-bug delay_span_bug 2021-02-07 01:44:29 -03:00			`\|`
			`LL \| fn main() {}`
			`\| ^^^^^^^^^`

Try to write the panic message with a single `write_all` call 2024-03-15 19:09:24 +01:00
Tweak ICE message Modify main message to be more conversational and emit one fewer note. 2023-02-07 19:17:24 +00:00			`error: the compiler unexpectedly panicked. this is a bug.`
Create ui test for -Ztreat-err-as-bug delay_span_bug 2021-02-07 01:44:29 -03:00
			`query stack during panic:`
Tweak delayed bug mentions. Now that we have both `delayed_bug` and `span_delayed_bug`, it makes sense to use the generic term "delayed bug" more. 2024-02-12 15:26:59 +11:00			`#0 [trigger_delayed_bug] triggering a delayed bug for testing incremental`
Create ui test for -Ztreat-err-as-bug delay_span_bug 2021-02-07 01:44:29 -03:00			`end of query stack`