unresolved-field error in interdependent workspace crates

[martijnarts]

I'm seeing an unresolved-field error on a field that definitely exists and compiles just fine. I think the problem is actually the weird dependencies I've introduced into my workspace modules though. I've reproduced it here: https://github.com/martijnarts/ra-unresolved-field-repro

I haven't tried to fully minimise the reproduction. It might be the case that this happens even without all the interdependencies and such, this is just the scenario that I see in my production code.

Here's what it looks like when breaking:

rust-analyzer version: 0.3.1426-standalone (0a956ec 2023-03-05)

rustc version: rustc 1.66.0 (69f9c33d7 2022-12-12)

relevant settings: happens in a basic, unconfigured rust/rust-analyzer setup.

[lnicola]

Probably a dupe of #14167.

It works if you remove the dev-dependency on crate-c from crate-b.

[martijnarts]

Ah yes it's definitely a dupe of that!