Unresolvable path for the const Self::MAX_DIGITS in a struct in core

[nicola-gigante]

Hi all,

I've made much progress in my project which is extracting syntactic and semantic information from rust crates and their dependencies (down to std and core) using rust-analyzer. Thanks for all the previous feedback!

Now while traversing core I find this particular instance of the reference of a const in the declaration of an array field of a struct, for which Semantics::resolve_path() returns None.

It happens for the path Self::MAX_DIGITS here in core.

I can reproduce the problem while analyzing the following code in a stand-alone crate:

pub struct Repro {
    pub x: [u8; Self::REPRO],
}

impl Repro {
    pub const REPRO: usize = 42;
}

I've not opened an issue because I don't know if I'm misusing resolve_path() somehow. Is this supposed to work like this for some reason?

Any help is appreciated :)

[ChayimFriedman2]

Support for constants in types was historically pretty weak. Just recently we completed the foundational work that allows to support resolving this path, that is, since recently (#21823) there is an InferenceResult for this const that can be used to resolve the path. I'm not sure if recent versions also support IDE's resolve_path() here, but if not, this will come soon.

[nicola-gigante]

Oh, I've updated from 0.0.322 to 0.0.327 and the problem disappeared!

Thanks again!