about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
diff options
context:
space:
mode:
authorMara Bos <m-ou.se@m-ou.se>2021-02-04 21:10:36 +0100
committerGitHub <noreply@github.com>2021-02-04 21:10:36 +0100
commit87b269ab6654ddcaed43933ebcd3754d000117b7 (patch)
tree97f1329a2518b204ea50c667272fb2db77f872a8 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
parentc5990dd8ad83fa1dccbc105102bceca0728977c3 (diff)
parent0870c154b63319df131de822d85dcebcbba080af (diff)
downloadrust-87b269ab6654ddcaed43933ebcd3754d000117b7.tar.gz
rust-87b269ab6654ddcaed43933ebcd3754d000117b7.zip
Rollup merge of #81645 - m-ou-se:panic-lint, r=estebank,flip1995
Add lint for `panic!(123)` which is not accepted in Rust 2021.

This extends the `panic_fmt` lint to warn for all cases where the first argument cannot be interpreted as a format string, as will happen in Rust 2021.

It suggests to add `"{}",` to format the message as a string. In the case of `std::panic!()`, it also suggests the recently stabilized
`std::panic::panic_any()` function as an alternative.

It renames the lint to `non_fmt_panic` to match the lint naming guidelines.

![image](https://user-images.githubusercontent.com/783247/106520928-675ea680-64d5-11eb-81f7-d8fa48b93a0b.png)

This is part of #80162.

r? ```@estebank```
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions