-
Notifications
You must be signed in to change notification settings - Fork 2k
Description
rust-analyzer version: 0.4.2790-standalone
rustc version: rustc 1.93.1 (01f6ddf75 2026-02-11)
editor or extension: vscode 1.109.2 RA 0.4.2790 and 0.3.2786
relevant settings:
"rust-analyzer.files.exclude": [
"/target",
"/crates/unnamed_crate",
],repository link (if public, optional): my main git server is dead due to a hard drive failure so i dont have a repo link available at the moment
code snippet to reproduce:
im not entirely sure what specifically changed, but i have a multi project cargo workspace setup like:
cataclysm: binary depends on nexus and dynamically depends on unnamed_crate via interfaces in nexus
nexus: library depends on nothing
unnamed_crate: library depends on nexus
omnispex: binary depends on nexus
cataclysm is fairly complicated? and uses things like pub use module::*;
telescopically so i can have a different main function based on compile target, but all that was working fine for the past year or so
theres nothing of note in RA logs, i wish i had more information but this issue really is weird, it occurs whenever it feels like it and over the past few years ive been using RA it only happens with cargo workspaces, heres the workspace root Cargo.toml:
[workspace]
resolver = "3"
members = ["crates/*"]
[profile.release]
opt-level = 3
lto = true
codegen-units = 1
panic = "unwind"
strip = "debuginfo"
[profile.release.package."*"]
opt-level = 3
codegen-units = 1
strip = "debuginfo"
[profile.dev.package."*"]
opt-level = 3
codegen-units = 1
[profile.wasm-release]
inherits = "release"
opt-level = "z"
strip = trueim at a loss of where to look for more information to help, any suggestions or instructions are welcome, i might be able to put the codebase on github without unnamed_crate, but i can probably leave a substitute in its place if its related to the issue