Conditional features limit with rust-analyzer?

[raycoe]

Hi,

Is there any limit in the number of features supported by rust-analyzer?
We have a project with about 25 features enabling us to (de)activate functionalities depending on the context, however we are a bit stuck using VSCode/rust-analyzer on Linux (Debian 13/Gnome) and MacOS Sequoia.

Thanks in advance
Ray

rust-analyzer version: 0.3.2660

rustc version: 1.90.0

editor or extension: VSCode 1.105.1

cargo.toml features def:

...
[features]
default = [ "all_features" ]
...

utils/mod.rs conditional cfg:

#[cfg(any(feature = "all_features", feature = "encoding"))]
pub mod iencoding;

Error raised by rust-analyzer:

utils/src/datasources/xml_reader.rs:237:54
    |
237 | ...                   Ok(s) => swappables::iencoding::HtmlEntity::get_decoded_str(&s.to_string()),
    |                                            ^^^^^^^^^ could not find `iencoding` in `swappables`
    |
note: found an item that was configured out
   --> utils/src/swappables/mod.rs:63:9
    |
 62 | #[cfg(any(feature = "all_features", feature = "encoding"))]
    |          ------------------------------------------------ the item is gated here
 63 | pub mod iencoding;

Wheras running cargo check/test doesn't raise any issue:

cargo test flib_utils_xml_reader_10
   Compiling utils v2.0.0 
    Finished `test` profile [unoptimized + debuginfo] target(s) in 1.00s
     Running unittests src/lib.rs (target/debug/deps/utils-ec548358a71e13e2)

running 1 test
test datasources::unit_tests::unit_test::flib_utils_xml_reader_10 ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 75 filtered out; finished in 0.00s

[ShoyuVanilla]

Error raised by rust-analyzer:

Where does it appear? Output panel on vs-code?

[raycoe]

No error when run directly in terminal

~/Documents/glbcreditslib/Head/utils$ cargo check --workspace
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.18s

[ShoyuVanilla]

With other trailing flags and env vars as well?

[raycoe]

Yes

~/Documents/glbcreditslib/Head/utils$ cargo check --workspace --manifest-path /home/dev/Documents/glbcreditslib/Head/utils/Cargo.toml --keep-going --all-targets
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.12s

[ShoyuVanilla]

That's still lacks of some of other flags and env vars. Why on earth do you think they are same?

If the very same command still fails to reproduce the compilation errors, that's probably emitted while checking util as a dependency for other crates in your workspace, not util itself. As running it in rust-analyzer has almost different from running it from your terminal. So, please check other commands in your output log as well.

That's the best what I can say about this regarding the given situation.

[raycoe]

You are right:
I run the following in system terminal from each directory corresponding to the projects depending on utils, no error emitted.

cd "/home/dev/Documents/glbcreditslib/Head/utils" && CARGO_LOG="cargo::core::compiler::fingerprint=info" RUSTUP_AUTO_INSTALL="0" RUSTUP_TOOLCHAIN="/home/dev/.rustup/toolchains/stable-x86_64-unknown-linux-gnu" "/home/dev/.cargo/bin/cargo" "check" "--workspace" "--message-format=json-diagnostic-rendered-ansi" "--manifest-path" "/home/dev/Documents/glbcreditslib/Head/utils/Cargo.toml" "--keep-going" "--all-targets"
...
{"reason":"build-finished","success":true}
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.14s

Then I created a new fresh workspace and added progressively all crates depending on utils until the error was emitted and finally found the one causing the issue.
As neither flycheck or diagnostic was emetting error referencing the root cause crate but the utils crate only, I'm wondering if features are finally the right approach in our context since we have so many applications depending on. The downside currently being that we have to release into production an application (the root cause crate) that was not amended apart from, now, a change in the toml.
Anyway, that's another topic...

Thanks for your help!

[ChayimFriedman2]

Does running cargo check --workspace also work?

[raycoe]

Yes, without problem

cargo check --workspace
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.48s

[ChayimFriedman2]

What are your rust-analyzer settings?

[raycoe]

Sorry if it is a silly question: do you want the 199 settings relating to rust-analyzer? Can I export them?

[ChayimFriedman2]

I want the settings you changed.

[raycoe]

Only one setting:

Settings/Features/Terminal "Terminal › Integrated: Cwd = ${workspaceFolder}