rust/tests/ui/resolve/issue-100365.rs

fn main() {
    let addr = Into::<std::net::IpAddr>.into([127, 0, 0, 1]);
    //~^ ERROR expected value, found trait `Into`
    //~| HELP use the path separator

    let _ = Into.into(());
    //~^ ERROR expected value, found trait `Into`
    //~| HELP use the path separator

    let _ = Into::<()>.into;
    //~^ ERROR expected value, found trait `Into`
    //~| HELP use the path separator
}

macro_rules! Trait {
    () => {
        ::std::iter::Iterator
        //~^ ERROR expected value, found trait `std::iter::Iterator`
        //~| ERROR expected value, found trait `std::iter::Iterator`
    };
}

macro_rules! create {
    () => {
        Into::<String>.into("")
        //~^ ERROR expected value, found trait `Into`
        //~| HELP use the path separator
    };
}

fn interaction_with_macros() {
    //
    // Note that if the receiver is a macro call, we do not want to suggest to replace
    // `.` with `::` as that would be a syntax error.
    // Since the receiver is a trait and not a type, we cannot suggest to surround
    // it with angle brackets. It would be interpreted as a trait object type void of
    // `dyn` which is most likely not what the user intended to write.
    // `<_ as Trait!()>::` is also not an option as it's equally syntactically invalid.
    //

    Trait!().map(std::convert::identity); // no `help` here!

    Trait!().map; // no `help` here!

    //
    // Ensure that the suggestion is shown for expressions inside of macro definitions.
    //

    let _ = create!();
}