allow_unwrap_types

What it does

allow_unwrap_types configures unwrap_used to allow any type in a given list of types to be unwrapped.

Advantage

Avoids the need to #[allow] unwrap() various types.

A concrete example is to allow unwrap() of std::sync::LockResult which is produced by locking a Mutex.

Drawbacks

None.

Example

#[allow(clippy::unwrap_used)]
some_mutex
    .lock()
    .unwrap()
    ...;

Could be written as:

some_mutex
    .lock()
    .unwrap()
    ...;

with the following in Cargo.toml:

[lints.clippy]
allow_unwrap_types = [std::sync::LockResult]

Comparison with existing lints

When the unwrap_used lint is applied, the user is forced to pepper their code with #[allow(clippy::unwrap_used)] when, for example, Mutex lock results are unwrapped.

Additional Context

The reasonableness of unwrapping LockResult is discussed here: https://www.reddit.com/r/rust/comments/10f6328/is_this_a_reasonable_way_to_handle_unwrapping/.

No files or tests are named. Start with Clippy's existing unwrap_used lint and the configuration shown in the issue, then trace how lint settings and type lists are handled. Done means allow_unwrap_types accepts the listed types and permits matching unwrap() calls without an explicit allow.