about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
diff options
context:
space:
mode:
authorYuki Okushi <jtitor@2k36.org>2021-07-07 12:17:39 +0900
committerGitHub <noreply@github.com>2021-07-07 12:17:39 +0900
commit7e95290caab37233eebc323351d353ecdb3ce782 (patch)
tree74fb4e3975a17a482e356dea4b235482b912d547 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
parent9bbc470e9779436d787ccda9924826176030b714 (diff)
parentd4e384bc1de0c11f3bc6fffc013358de85ad2982 (diff)
downloadrust-7e95290caab37233eebc323351d353ecdb3ce782.tar.gz
rust-7e95290caab37233eebc323351d353ecdb3ce782.zip
Rollup merge of #86717 - rylev:rename, r=nikomatsakis
Rename some Rust 2021 lints to better names

Based on conversation in https://github.com/rust-lang/rust/issues/85894.

Rename a bunch of Rust 2021 related lints:

Lints that are officially renamed because they are already in beta or stable:
* `disjoint_capture_migration` => `rust_2021_incompatible_closure_captures`
* `or_patterns_back_compat` => `rust_2021_incompatible_or_patterns`
* `non_fmt_panic` => `non_fmt_panics`

Lints that are renamed but don't require any back -compat work since they aren't yet in stable:
* `future_prelude_collision` => `rust_2021_prelude_collisions`
* `reserved_prefix` => `rust_2021_token_prefixes`

Lints that have been discussed but that I did not rename:
* ~`non_fmt_panic` and `bare_trait_object`: is making this plural worth the headache we might cause users?~
* `array_into_iter`: I'm unsure of a good name and whether bothering users with a name change is worth it.

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