.max() flagged as having 0 arguments

[jinschoi]

rust-analyzer version: rust-analyzer 1.83.0 (90b35a62 2024-11-26)
rustc version: rustc 1.83.0 (90b35a623 2024-11-26)
editor or extension: Emacs 29.3, Zed 0.166.1
repository link (if public, optional): example
code snippet to reproduce:

fn test_max<A, B>()
where
    A: IntoIterator<Item = usize>,
    B: IntoIterator<Item = usize>,
{
    let _ = 1.max(2);
}

This has been reported several times, see #11048 and #10673, probably more. It's come up for me now. I was able to cut it way down to the example above. Remove either of the type constraints and it's happy. I also tried other traits, couldn't find one that caused the issue.

It wasn't doing this earlier.

[Tunixer]

fn test_max<A, B>()
where
    A: IntoIterator<Item = usize>,
    B: IntoIterator<Item = usize>,
{
    let _ = 1.max(2);
}
fn main() {
    let vec1 = vec![1, 2, 3];
    let vec2 = vec![4, 5, 6];

    test_max::<Vec<usize>, Vec<usize>>( );

    println!("Hello, world!");
}

I have used this demo on my test enviromment. But the rust-analyzer mark the max() as core::cmp::Ord correctly.

rust-analyzer version: 0.3.2237-standalone (59bc7b4 2024-12-29)

[jinschoi]

I don't understand. Does that mean it is fixed in nightly? Great, but I can't test it myself because only stable provides rust-analyzer.

[flodiebold]

This is #10653. It'll probably get fixed with the new trait solver.