rust/tests/ui/resolve/bad-expr-path2.rs

mod m1 {
    pub mod arguments {}
}

fn main(arguments: Vec<String>) { //~ ERROR `main` function has wrong type
    log(debug, m1::arguments);
    //~^ ERROR cannot find function `log` in this scope
    //~| ERROR cannot find value `debug` in this scope
    //~| ERROR expected value, found module `m1::arguments`
}
Print an error if we try to refer to a module in an expr_path. 2011-01-25 18:15:19 -05:00			`mod m1 {`
Make the maximum edit distance of typo suggestions a function of the typo'd name's length. 2015-06-07 17:56:18 -07:00			`pub mod arguments {}`
Print an error if we try to refer to a module in an expr_path. 2011-01-25 18:15:19 -05:00			`}`

Add backticks to various diagnostics 2020-01-05 00:17:46 +00:00			fn main(arguments: Vec<String>) { //~ ERROR `main` function has wrong type
Make the maximum edit distance of typo suggestions a function of the typo'd name's length. 2015-06-07 17:56:18 -07:00			`log(debug, m1::arguments);`
resolve: Do not use "resolve"/"resolution" in error messages 2017-01-12 01:18:08 +03:00			//~^ ERROR cannot find function `log` in this scope
			//~\| ERROR cannot find value `debug` in this scope
More systematic error reporting in path resolution 2016-12-01 01:35:25 +03:00			//~\| ERROR expected value, found module `m1::arguments`
test: Make manual changes to deal with the fallout from removal of `~[T]` in test, libgetopts, compiletest, librustdoc, and libnum. 2014-03-05 15:28:08 -08:00			`}`