rust/src/test/ui-fulldeps/lint-group-plugin.rs

// run-pass
// aux-build:lint_group_plugin_test.rs
// ignore-stage1
#![feature(plugin)]
#![plugin(lint_group_plugin_test)]
#![allow(dead_code)]

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

#[allow(lint_me)]
pub fn main() {
    fn lintme() { }

    fn pleaselintme() { }
}
Introduce 'run-pass' header to 'ui' tests in compiletest. Fix issue #36516. The 'run-pass' header cause a 'ui' test to execute the result. It is used to test the lint output, at the same time ensure those lints won't cause the source code to become compile-fail. 12 run-pass/run-pass-fulldeps tests gained the header and are moved to ui/ui-fulldeps. After this move, no run-pass/run-pass-fulldeps tests should rely on the compiler's JSON message. This allows us to stop passing `--error-format json` in run-pass tests, thus fixing #36516. 2017-05-13 17:54:50 +08:00			`// run-pass`
Add lint groups; define built-in lint groups `bad_style` and `unused` This adds support for lint groups to the compiler. Lint groups are a way of grouping a number of lints together under one name. For example, this also defines a default lint for naming conventions, named `bad_style`. Writing `#[allow(bad_style)]` is equivalent to writing `#[allow(non_camel_case_types, non_snake_case, non_uppercase_statics)]`. These lint groups can also be defined as a compiler plugin using the new `Registry::register_lint_group` method. This also adds two built-in lint groups, `bad_style` and `unused`. The contents of these groups can be seen by running `rustc -W help`. 2014-07-21 15:27:59 +12:00			`// aux-build:lint_group_plugin_test.rs`
			`// ignore-stage1`
Replace #[phase] with #[plugin] / #[macro_use] / #[no_link] 2014-12-31 20:43:46 -08: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 13:56:38 -08:00			`#![plugin(lint_group_plugin_test)]`
Fix compiletest so it respects warnings for run-pass. 2016-08-22 16:51:37 -07:00			`#![allow(dead_code)]`
Add lint groups; define built-in lint groups `bad_style` and `unused` This adds support for lint groups to the compiler. Lint groups are a way of grouping a number of lints together under one name. For example, this also defines a default lint for naming conventions, named `bad_style`. Writing `#[allow(bad_style)]` is equivalent to writing `#[allow(non_camel_case_types, non_snake_case, non_uppercase_statics)]`. These lint groups can also be defined as a compiler plugin using the new `Registry::register_lint_group` method. This also adds two built-in lint groups, `bad_style` and `unused`. The contents of these groups can be seen by running `rustc -W help`. 2014-07-21 15:27:59 +12:00
			`fn lintme() { } //~ WARNING item is named 'lintme'`
			`fn pleaselintme() { } //~ WARNING item is named 'pleaselintme'`

			`#[allow(lint_me)]`
			`pub fn main() {`
			`fn lintme() { }`

			`fn pleaselintme() { }`
			`}`