…ixes rust-lang#7106)

…ffen

Unused io amount detects `.read().ok()?`

fixes rust-lang#7096
changelog: unused_io_amount now detect expertion like `.read().ok()?`,  `.read().or_else(|err| ...)?` and similar expressions.

`single_component_path_imports`: ignore `pub(crate) use some_macro;`

Fixes rust-lang#7106

*Please write a short comment explaining your change (or "none" for internal only changes)*

changelog: Ignore exporting a macro within a crate using `pub(crate) use some_macro;` for [`single_component_path_imports`]

Fix lintcheck on windows

changelog: None

cloned_instead_of_copied MSRV

changelog: none
(since the lint is still new)

Fixes rust-lang#7127

r? `@Manishearth`

Adds support for symbol resolution on illumos systems.

…Manishearth

extend `single_element_loop` to match `.iter()`

This extends `single_element_loop` to also match `[..].iter()` in the loop argument. Related to rust-lang#7125, but not completely fixing it due to the lint only firing if the array expression contains a local variable.

---

changelog: none

Finish MSRV for cloned_instead_of_copied

changelog: none

r? `@Manishearth`

…sion

Refactor MSRV aliases

changelog: Remove MSRV from `needless_question_mark` and change MSRV for `missing_const_for_fn` from 1.37.0 to 1.46.0.

First [mentioned on Zulip](https://rust-lang.zulipchat.com/#narrow/stream/257328-clippy/topic/Better.20MSRV.20testing.20idea/near/236215074).

* Moves MSRV constants into `clippy_utils::msrvs`. Now they are named to represent a stabilized feature flag or library item that is required for a lint's suggestion.
* `needless_question_mark` no longer has MSRV. Not needed since it does not suggest adding `?`.
* `missing_const_for_fn` MSRV was changed from 1.37.0 to 1.46.0. This seems to be a past mistake.

…alid_sugg_macro_expansion, r=llogiq

manual_unwrap_or: fix invalid code suggestion, due to macro expansion

fixes rust-lang#6965

changelog: fix invalid code suggestion in `manual_unwrap_or` lint, due to macro expansion

…FN_with_large_array, r=Manishearth

Fix FN in `iter_cloned_collect` with a large array

fixes rust-lang#6808
changelog: Fix FN in `iter_cloned_collect` with a large array

I spotted that [is_iterable_array](https://github.com/rust-lang/rust-clippy/blob/a362a4d1d0edb66aef186c1d27b28c60573078f4/clippy_lints/src/loops/explicit_iter_loop.rs#L67-L75) function that `explicit_iter_loop` lint is using only works for array sizes <= 32.
There is this comment:
> IntoIterator is currently only implemented for array sizes <= 32 in rustc

I'm a bit confused, because I read that [IntoIterator for arrays](https://doc.rust-lang.org/src/core/array/mod.rs.html#194-201) with const generic `N` is stable since = "1.0.0". Although Const Generics MVP were stabilized in Rust 1.51.

Should I set MSRV for the current change? I will try to test with older compilers soon.

Fix ICE checking for feature gated const fn

fixes: rust-lang#7126
changelog: Fix ICE in `missing_const_for_fn` when using a feature-gated `const fn`

…k-Simulacrum

Ignore nonstandard lldb version strings in compiletest

Fixes rust-lang#84131

Unsure if I should do the same for the Apple LLDB branch above.

Reuse modules on `hermit`

Reuse the following modules on `hermit`:
- `unix::path` (contents identical)
- `unsupported::io` (contents identical)
- `unsupported::thread_local_key` (contents functionally identical, only changes are the panic error messages)

`@rustbot` label: +T-libs-impl

…imulacrum

Update backtrace to 0.3.57

Adds support for symbol resolution on illumos systems.

…ip1995

Update Clippy

Out of cycle sync: I want to get rust-lang/rust-clippy#7129 into beta that is branched next week.

This sync only adds one new feature in efc4c6c, which looks fine to me. Otherwise it only contains bug fixes and/or restricts lints further.

r? `@Manishearth`

move representability checks to rustc_ty_utils