diff options
| author | bors <bors@rust-lang.org> | 2023-11-26 22:28:13 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-11-26 22:28:13 +0000 |
| commit | f30a859ae32c97668a1a8473fc95b72857073e37 (patch) | |
| tree | f4d56a4acb559514cf78f368f0665f0d4891041f /tests/rustdoc-js-std/parser-errors.js | |
| parent | 2c56b4f800332e0b07c5cde6b5c2d663f2079d59 (diff) | |
| parent | 5689a86fb8a8e33435d60f9e8f5bb760ac0dad80 (diff) | |
| download | rust-f30a859ae32c97668a1a8473fc95b72857073e37.tar.gz rust-f30a859ae32c97668a1a8473fc95b72857073e37.zip | |
Auto merge of #11867 - y21:implied_bounds_in_impls_complexity, r=Jarcho
Move `implied_bounds_in_impls` back to complexity This lint was originally in the complexity category when I PR'd it. It was then moved to nursery by me due to a number of issues (a false positive, an invalid suggestion and an ICE), but that was probably an overreaction and all of the issues were fixed quickly after. This is a useful lint imo and there hasn't been any issues with it in a few months, so I say we should give it another try and move it back to complexity. I did a lintcheck run on the top 400 crates and all of them are legitimate, with 18 warnings. Most of them are from anstyle having a `impl Display + Copy + Clone` return type, or the bitvec crate with a return type like `impl Iterator + DoubleEndedIterator`. changelog: Move [`implied_bounds_in_impls`] to `complexity` (Now warn-by-default) [#11867](https://github.com/rust-lang/rust-clippy/pull/11867)
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions