os-rust/tests/ui-fulldeps/lint-plugin-forbid-attrs.rs

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

#![feature(plugin)]
#![plugin(lint_plugin_test)]
//~^ WARN use of deprecated attribute `plugin`
#![forbid(test_lint)]

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

#[allow(test_lint)]
//~^ ERROR allow(test_lint) incompatible
//~| ERROR allow(test_lint) incompatible
pub fn main() {
    lintme();
}
Moved issue tests to subdirs and normalised names. 2019-03-12 00:49:17 +00:00			`// aux-build:lint-plugin-test.rs`
Test lint plugins 2014-06-18 13:46:48 -07:00			`// 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_plugin_test)]`
--bless ui-fulldeps tests 2019-10-03 09:33:28 +02:00			//~^ WARN use of deprecated attribute `plugin`
Test lint plugins 2014-06-18 13:46:48 -07:00			`#![forbid(test_lint)]`

Use true previous lint level when detecting overriden forbids Previously, cap-lints was ignored when checking the previous forbid level, which meant that it was a hard error to do so. This is different from the normal behavior of lints, which are silenced by cap-lints; if the forbid would not take effect regardless, there is not much point in complaining about the fact that we are reducing its level. It might be considered a bug that even `--cap-lints deny` would suffice to silence the error on overriding forbid, depending on if one cares about failing the build or precisely forbid being set. But setting cap-lints to deny is quite odd and not really done in practice, so we don't try to handle it specially. This also unifies the code paths for nested and same-level scopes. However, the special case for CLI lint flags is left in place (introduced by #70918) to fix the regression noted in #70819. That means that CLI flags do not lint on forbid being overridden by a non-forbid level. It is unclear whether this is a bug or a desirable feature, but it is certainly inconsistent. CLI flags are a sufficiently different "type" of place though that this is deemed out of scope for this commit. 2020-11-07 18:14:38 -05:00			`fn lintme() {} //~ ERROR item is named 'lintme'`
Test lint plugins 2014-06-18 13:46:48 -07:00
Update E0453 to new error format Fixes #35929. Part of #35233. r? @jonathandturner 2016-08-25 19:09:48 +05:30			`#[allow(test_lint)]`
Use true previous lint level when detecting overriden forbids Previously, cap-lints was ignored when checking the previous forbid level, which meant that it was a hard error to do so. This is different from the normal behavior of lints, which are silenced by cap-lints; if the forbid would not take effect regardless, there is not much point in complaining about the fact that we are reducing its level. It might be considered a bug that even `--cap-lints deny` would suffice to silence the error on overriding forbid, depending on if one cares about failing the build or precisely forbid being set. But setting cap-lints to deny is quite odd and not really done in practice, so we don't try to handle it specially. This also unifies the code paths for nested and same-level scopes. However, the special case for CLI lint flags is left in place (introduced by #70918) to fix the regression noted in #70819. That means that CLI flags do not lint on forbid being overridden by a non-forbid level. It is unclear whether this is a bug or a desirable feature, but it is certainly inconsistent. CLI flags are a sufficiently different "type" of place though that this is deemed out of scope for this commit. 2020-11-07 18:14:38 -05:00			`//~^ ERROR allow(test_lint) incompatible`
			`//~\| ERROR allow(test_lint) incompatible`
Test lint plugins 2014-06-18 13:46:48 -07:00			`pub fn main() {`
			`lintme();`
			`}`