How do I fix E0432 (unresolved import)?

Enable the feature: Fix the path: Use crate:: from the root, super:: from a child module.

Rust errors / Names, paths and imports

Rust compiler error · checked with rustc 1.99.0

Rust error E0432: unresolved import

Q: What does Rust error E0432 mean?

A use path points at something that does not exist: a wrong path, a missing dependency or feature, or a module not declared.

What it meansA use path points at something that does not exist: a wrong path, a missing dependency or feature, or a module not declared.

What rustc prints

error[E0432]: unresolved import `something`
 --> main.rs:1:5
  |
1 | use something::Foo; // error: unresolved import `something::Foo`.
  |     ^^^^^^^^^ use of unresolved module or unlinked crate `something`
  |
  = help: you might be missing a crate named `something`

Real output of rustc 1.99.0 compiling the official example below (2021 edition). Your names and line numbers will differ; the first line is the part to match.

Why it happens

A crate feature is off (for example serde's derive or tokio's full).
The path moved between crate versions.
Using crate:: vs a module-relative path incorrectly.

How to fix it

1. Enable the feature

cargo add serde --features derive
cargo add tokio --features full

2. Fix the path

Use crate:: from the root, super:: from a child module.

use crate::db::Pool;

Other wordings of this error

unresolved import, no `, in the root, could not find

E0432Names, paths and imports

Activein rustc 1.99.0

7related errors linked below

The compiler team's explanation

An import was unresolved.

Erroneous code example:

use something::Foo; // error: unresolved import `something::Foo`.

In Rust 2015, paths in use statements are relative to the crate root. To import items relative to the current and parent modules, use the self:: and super:: prefixes, respectively.

In Rust 2018 or later, paths in use statements are relative to the current module unless they begin with the name of a crate or a literal crate::, in which case they start from the crate root. As in Rust 2015 code, the self:: and super:: prefixes refer to the current and parent modules respectively.

Also verify that you didn't misspell the import name and that the import exists in the module from where you tried to import it. Example:

use self::something::Foo; // Ok.

mod something {
    pub struct Foo;
}

If you tried to use a module from an external crate and are using Rust 2015, you may have missed the extern crate declaration (which is usually placed in the crate root):

extern crate core; // Required to use the `core` crate in Rust 2015.

use core::any;

Since Rust 2018 the extern crate declaration is not required and you can instead just use it:

use core::any; // No extern crate required in Rust 2018.

From rustc --explain E0432 (1.99.0), part of the Rust project, MIT or Apache-2.0. Official page.

Up next

Often hit nextE0425: cannot find value in this scopeA related error from the same family.Read it next →

Also worth your time

Did this answer your question?