rust/src/test/ui-fulldeps/lint-plugin-forbid-cmdline.rs

// aux-build:lint-plugin-test.rs
// ignore-stage1
// compile-flags: -F test-lint

#![feature(plugin)]
#![plugin(lint_plugin_test)]

fn lintme() { } //~ ERROR item is named 'lintme'

#[allow(test_lint)] //~ ERROR allow(test_lint) overruled by outer forbid(test_lint)
pub fn main() {
    lintme();
}
Moved issue tests to subdirs and normalised names. 2019-03-11 19:49:17 -05:00			`// aux-build:lint-plugin-test.rs`
Test lint plugins 2014-06-18 15:46:48 -05:00			`// ignore-stage1`
			`// compile-flags: -F test-lint`

Replace #[phase] with #[plugin] / #[macro_use] / #[no_link] 2014-12-31 22:43:46 -06:00			`#![feature(plugin)]`
Use a crate attribute to load plugins #[plugin] #[no_link] extern crate bleh; becomes a crate attribute #![plugin(bleh)] The feature gate is still required. It's almost never correct to link a plugin into the resulting library / executable, because it will bring all of libsyntax and librustc with it. However if you really want this behavior, you can get it with a separate `extern crate` item in addition to the `plugin` attribute. Fixes #21043. Fixes #20769. [breaking-change] 2015-02-06 15:56:38 -06:00			`#![plugin(lint_plugin_test)]`
Test lint plugins 2014-06-18 15:46:48 -05:00
			`fn lintme() { } //~ ERROR item is named 'lintme'`

			`#[allow(test_lint)] //~ ERROR allow(test_lint) overruled by outer forbid(test_lint)`
			`pub fn main() {`
			`lintme();`
			`}`