clippy::unnecessary_literal_unwrap: used `unwrap()` on `Some` value

What you see

warning: used `unwrap()` on `Some` value
 --> main.rs:3:12
  |
3 | let val1 = Some(1).unwrap();
  |            ^^^^^^^^^^^^^^^^
  |
  = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#unnecessary_literal_unwrap
  = note: `#[warn(clippy::unnecessary_literal_unwrap)]` on by default
help: remove the `Some` and `unwrap()`
  |
3 - let val1 = Some(1).unwrap();
3 + let val1 = 1;
  |

Real output of Clippy 0.1.99 (Rust 1.99) on the example below. Names and line numbers in yours will differ.

Does it matter?

It is better to write the value directly without the indirection.

Code that does something simple in a complicated way. Warns by default.

How to fix it

Clippy can fix this one for you: run cargo clippy --fix (add --allow-dirty if you have uncommitted changes). Review the diff before you commit.

Flagged

let val1 = Some(1).unwrap();
let val2 = Ok::<_, ()>(1).unwrap();
let val3 = Err::<(), _>(1).unwrap_err();

Write this instead

let val1 = 1;
let val2 = 1;
let val3 = 1;

Turn it off, or on

Allow it where it does not fit your code, as narrowly as you can:

#[allow(clippy::unnecessary_literal_unwrap)]
fn my_function() { /* ... */ }

[lints.clippy]
unnecessary_literal_unwrap = "allow"

cargo clippy -- -A clippy::unnecessary-literal-unwrap

The [lints] table needs Rust 1.74 or newer. In a workspace, put it under [workspace.lints.clippy] and add [lints] workspace = true to each member.