rust/tests/ui/resolve/resolve-pseudo-shadowing.rs

// run-pass
// check that type parameters can't "shadow" qualified paths.

fn check<Clone>(_c: Clone) {
    fn check2() {
        let _ = <() as std::clone::Clone>::clone(&());
    }
    check2();
}

fn main() { check(()); }
tests: Add missing run-pass annotations 2019-07-27 00:54:25 +03:00			`// run-pass`
resolve: don't speculatively create freevars when resolving Fixes #29522 2015-11-03 20:44:23 +02:00			`// check that type parameters can't "shadow" qualified paths.`

			`fn check<Clone>(_c: Clone) {`
			`fn check2() {`
`#[must_use]` for associated functions is supposed to actually work In the comments of (closed, defunct) pull request #54884, Mazdak "Centril" Farrokhzad noted that must-use annotations didn't work on an associated function (what other communities might call a "static method"). Subsequent logging revealed that in this case we have a `Def::Method`, whereas the lint pass was only matching on `Def::Fn`. (One could argue that those def-names are thereby misleading—must-use for self-ful methods have always worked—but documenting or reworking that can be left to another day.) 2018-10-11 23:10:37 -07:00			`let _ = <() as std::clone::Clone>::clone(&());`
resolve: don't speculatively create freevars when resolving Fixes #29522 2015-11-03 20:44:23 +02:00			`}`
			`check2();`
			`}`

			`fn main() { check(()); }`