Rust-analyzer or VS code error

[dickytamara]

I have code like this

pub const fn test(a: i32, b: i32) -> [i32; 2] { [a, b] }

const LOOKUPVALUE: &'static [[i32;2]; 4] = &[
    test(0x0fab272b, 0x0fab272b), test(0x7e1d93ea, 0x7e1d93ea),
    test(0x0fab272b, 0x7e1d93ea), test(0x7e1d93ea, 0x0fab272b),
];

fn main() {
    //
    LOOKUPVALUE.iter().for_each(|x| println!("{:?}", x))

}

Vs-code

please look at variable that printed on const LOOKUPVALUE "a:" and "b:"

[bjorn3]

Duplicate of #7434

[flodiebold]

I don't think this is related to #7434. (That issue is about const parameters, not bodies of const items, which we do already handle.)

The issue is a bit unclear, but I think what @dickytamara is referring to is that the parameter hints a: and b: only show up in some of the calls. My guess is that our heuristics are a bit too eager there; notice that the arguments where the hints are hidden end in a resp. b.

[dickytamara]

here another example, like @flodiebold says heruistic more resonable for now

[Veykril]

The problem is that we check if the expression has the argument name as a prefix or postfix and since your hexadecimal numbers have a trailing a or b the parameter hints disappear respectively. We shouldn't just check every expression like that but only some of them, mainly field access, paths and method_calls I guess?

[dickytamara]

yes @Veykril , hints disappear when we have same postfix. i found this when editing large set of predefined table value.