rust/tests/ui-internal/custom_ice_message.stderr

thread '<unnamed>' panicked at 'Would you like some help with that?', clippy_lints/src/utils/internal_lints/produce_ice.rs
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

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

note: we would appreciate a bug report: https://github.com/rust-lang/rust-clippy/issues/new

note: rustc <version> running on <target>

note: compiler flags: -C prefer-dynamic -Z ui-testing

query stack during panic:
thread panicked while processing panic. aborting.
Merge commit '149392b0baa4730c68f3c3eadf5c6ed7b16b85a4' into clippyup 2023-02-25 18:08:29 -06:00			`thread '<unnamed>' panicked at 'Would you like some help with that?', clippy_lints/src/utils/internal_lints/produce_ice.rs`
Update custom_ice_message.stderr 2020-01-16 09:01:31 -06:00			note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Add custom ICE message that points to Clippy repo This utilizes https://github.com/rust-lang/rust/pull/60584 by setting our own `panic_hook` and pointing to our own issue tracker instead of the rustc issue tracker. This also adds a new internal lint to test the ICE message. Potential downsides * This essentially copies rustc's `report_ice` function as `report_clippy_ice`. I think that's how it's meant to be implemented, but maybe @jonas-schievink could have a look as well =) The downside of more-or-less copying this function is that we have to maintain it as well now. The original function can be found [here][original]. * `driver` now depends directly on `rustc` and `rustc_errors` Closes #2734 [original]: https://github.com/rust-lang/rust/blob/59367b074f1523353dddefa678ffe3cac9fd4e50/src/librustc_driver/lib.rs#L1185 2019-09-27 00:09:12 -05:00
Merge commit '435a8ad86c7a33bd7ffb91c59039943408d3b6aa' into clippyup 2023-05-20 08:39:26 -05:00			`error: the compiler unexpectedly panicked. this is a bug.`
Add custom ICE message that points to Clippy repo This utilizes https://github.com/rust-lang/rust/pull/60584 by setting our own `panic_hook` and pointing to our own issue tracker instead of the rustc issue tracker. This also adds a new internal lint to test the ICE message. Potential downsides * This essentially copies rustc's `report_ice` function as `report_clippy_ice`. I think that's how it's meant to be implemented, but maybe @jonas-schievink could have a look as well =) The downside of more-or-less copying this function is that we have to maintain it as well now. The original function can be found [here][original]. * `driver` now depends directly on `rustc` and `rustc_errors` Closes #2734 [original]: https://github.com/rust-lang/rust/blob/59367b074f1523353dddefa678ffe3cac9fd4e50/src/librustc_driver/lib.rs#L1185 2019-09-27 00:09:12 -05:00
			`note: we would appreciate a bug report: https://github.com/rust-lang/rust-clippy/issues/new`

Merge commit '30448e8cf98d4754350db0c959644564f317bc0f' into clippyup 2023-06-02 04:41:57 -05:00			`note: rustc <version> running on <target>`
Merge commit '435a8ad86c7a33bd7ffb91c59039943408d3b6aa' into clippyup 2023-05-20 08:39:26 -05:00
			`note: compiler flags: -C prefer-dynamic -Z ui-testing`

Merge commit '30448e8cf98d4754350db0c959644564f317bc0f' into clippyup 2023-06-02 04:41:57 -05:00			`query stack during panic:`
			`thread panicked while processing panic. aborting.`