Rust New Added 8 September 2026

Rust: the `?` operator could not convert the error (E0277)

The ? operator converts the error with From, and no such conversion exists between the error you produced and the one your function returns. It is the most common friction point when a function starts touching two libraries with their own error types.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix

// Define the conversion once with thiserror
#[derive(thiserror::Error, Debug)]
pub enum AppError {
    #[error("io: {0}")]
    Io(#[from] std::io::Error),
    #[error("parse: {0}")]
    Parse(#[from] serde_json::Error),
}

// Application code that does not need typed errors
fn main() -> anyhow::Result<()> {
    let cfg: Config = serde_json::from_str(&std::fs::read_to_string("c.json")?)?;
    Ok(())
}

// One off: convert at the call site
.map_err(|e| AppError::Other(e.to_string()))?

How to diagnose Rust errors

Rust's compiler errors are unusually helpful. They are closer to a code review than an error message. Almost all of them come from ownership (a value was moved and then used), borrowing (two mutable borrows, or a borrow outliving its owner), or trait resolution (the required bound is not satisfied). The productive habit is to read the error's notes and help sections in full and run rustc --explain on the code.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

Run rustc --explain E0502 (or whichever code) for a worked explanation of the rule you violated.
For borrow conflicts, shorten the borrow's scope first, introducing a block or binding the intermediate result, before reaching for Rc<RefCell<T>>.
For moved-value errors, decide deliberately: clone (cost), borrow (lifetime), or restructure so ownership flows one way. Cloning to silence the compiler is fine early and worth revisiting later.
For trait errors, read which bound is missing and where it is required. cargo tree -d finds duplicate crate versions, which cause "trait not implemented" errors between two identical-looking types.
Use cargo clippy routinely; it catches idiom problems that later become borrow-checker fights.

Tools worth reaching for

rustc --explain
cargo clippy
cargo tree -d
cargo expand
RUST_BACKTRACE=1

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

doc.rust-lang.org

Related Rust errors

See all 19 Rust errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.