Clippy lint · Restriction · checked with Clippy 0.1.99

clippy::unused_result_ok: Checks for calls to Result::ok() without using the returned Option

What it meansChecks for calls to Result::ok() without using the returned Option. It is in the restriction group and off by default.

Does it matter?

Using Result::ok() may look like the result is checked like unwrap or expect would do but it only silences the warning caused by #[must_use] on the Result.

Lints that forbid language features for specific codebases (no unwrap, no indexing...). Off by default; pick them one by one, never the whole group.

How to fix it

Clippy does not fix this one automatically (its suggestion may change behaviour, so it only shows it). Change the code by hand:

Flagged

some_function().ok();

Write this instead

let _ = some_function();

Turn it off, or on

It is off by default. To use it, set it to warn or deny:

Whole crate (Cargo.toml)

[lints.clippy]
unused_result_ok = "warn"

In code

#![warn(clippy::unused_result_ok)]

One run

cargo clippy -- -W clippy::unused-result-ok

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.

Restrictiongroup

allowdefault level

nofixed by cargo clippy --fix

1.82.0added in Rust

Clippy's own documentation

What it does

Checks for calls to Result::ok() without using the returned Option.

Why is this bad?

Using Result::ok() may look like the result is checked like unwrap or expect would do but it only silences the warning caused by #[must_use] on the Result.

Example

some_function().ok();

Use instead:

let _ = some_function();

From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.

Up next

Also worth your time

Did this answer your question?