Email me

Clippy lints / Style

Clippy lint · Style · checked with Clippy 0.1.99

clippy::io_other_error: this can be `std::io::Error::other(_)`

What it meansClippy lint io_other_error. It is in the style group and warns by default.

What you see

warning: this can be `std::io::Error::other(_)`
 --> main.rs:4:9
  |
4 | let _ = io::Error::new(io::ErrorKind::Other, "bad".to_string());
  |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#io_other_error
  = note: `#[warn(clippy::io_other_error)]` on by default
help: use `std::io::Error::other`
  |
4 - let _ = io::Error::new(io::ErrorKind::Other, "bad".to_string());
4 + let _ = io::Error::other("bad".to_string());
  |

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?

Since Rust 1.74, there’s the io::Error::other(_) shortcut.

Code that works but is not idiomatic Rust. 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

use std::io;
let _ = io::Error::new(io::ErrorKind::Other, "bad".to_string());

Write this instead

let _ = std::io::Error::other("bad".to_string());

Turn it off, or on

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

On one item

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

Whole crate (Cargo.toml)

[lints.clippy]
io_other_error = "allow"

One run

cargo clippy -- -A clippy::io-other-error

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.

Settings in clippy.toml

  • msrv: The minimum rust version that the project supports. Defaults to the rust-version field in Cargo.toml
Stylegroup
warndefault level
yesfixed by cargo clippy --fix
1.87.0added in Rust

Clippy's own documentation

This lint warns on calling io::Error::new(..) with a kind of io::ErrorKind::Other.

Why is this bad?

Since Rust 1.74, there’s the io::Error::other(_) shortcut.

Example

use std::io;
let _ = io::Error::new(io::ErrorKind::Other, "bad".to_string());

Use instead:

let _ = std::io::Error::other("bad".to_string());

Configuration

  • msrv: The minimum rust version that the project supports. Defaults to the rust-version field in Cargo.toml

    (default: current version)

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

Related lints

All 847 Clippy lints · Rust compiler errors · Cargo.toml checker

Up next

Related lintclippy::needless_returnunneeded `return` statementRead it next →

Did this answer your question?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ