diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2021-06-29 08:46:14 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-06-29 08:46:14 +0900 |
| commit | 14f333597ed7307f8d6956eadc03ce09f284da82 (patch) | |
| tree | 0013df49c95419114de2e9c2c789bdf778d90ff6 /library/std/src/sys/unix/process/process_unix.rs | |
| parent | 22f2332b353c9522b31d004887dd6500aae55901 (diff) | |
| parent | 934e6058eb5b051eac862d611cbc73e58a09e6dd (diff) | |
| download | rust-14f333597ed7307f8d6956eadc03ce09f284da82.tar.gz rust-14f333597ed7307f8d6956eadc03ce09f284da82.zip | |
Rollup merge of #86671 - m-ou-se:non-fmt-panic-future-incompatible, r=nikomatsakis
Turn non_fmt_panic into a future_incompatible edition lint.
This turns the `non_fmt_panic` lint into a future_incompatible edition lint, so it becomes part of the `rust_2021_compatibility` group. See https://github.com/rust-lang/rust/issues/85894.
This lint produces both warnings about semantical changes (e.g. `panic!("{{")`) and things that will become hard errors (e.g. `panic!("{")`). So I added a `explain_reason: false` that supresses the default "this will become a hard error" or "the semantics will change" message, and instead added a note depending on the situation. (cc `@rylev)`
r? `@nikomatsakis`
Diffstat (limited to 'library/std/src/sys/unix/process/process_unix.rs')
0 files changed, 0 insertions, 0 deletions