rust-analyzer: `#[path = "../XXXXXX"]` attribute on modules gives false `unresolved-module` error

Example: https://github.com/WilliamVenner/rust-analyzer-broken-example

Code:

./package/src/main.rs

#[path = "../../silly_mod/mod.rs"]
mod silly_mod;

fn main() {
    silly_mod::hello();
}

./silly_mod/mod.rs

pub fn hello() {
	println!("Hello, world!");
}

About this issue

Original URL
State: open
Created 3 years ago
Reactions: 4
Comments: 17 (8 by maintainers)

Commits related to this issue

devenv(wasm): Fix autocompletion not working by symlink the updir then use `#[path = "symlink/file.rs"]` https://github.com/rust-lang/rust-analyzer/issues/9173 — committed to DrSensor/nusa by DrSensor 10 months ago

Most upvoted comments

Is there any way to suppress the error? I can live with “unknown” for the module content, but the red squiggles are distracting. 😃

Yeah, I have this in my settings

    "rust-analyzer.diagnostics.disabled": [
        "unlinked-file", // I guess for "normal" projects unlinked files are strange, for me they are common
        "missing-match-arm", // https://github.com/rust-lang/rust-analyzer/issues/4896
        "type-mismatch", // https://github.com/rust-lang/rust-analyzer/issues/1109
        "unresolved-module", // https://github.com/rust-lang/rust-analyzer/issues/9173
        "unresolved-extern-crate", // https://github.com/rust-lang/rust-analyzer/issues/12926
    ],

RalfJung on Aug 24, 2022

I’ve also just run into this issue, I guess the more idiomatic way to handle this situation is to make the referenced module into a full blown library referenced by path = "../path/to/module" in Cargo.toml?

kellpossible on Nov 14, 2021