rust/tests/ui/stability-attribute/issue-28075.rs

// Unstable entities should be caught in import lists

//@ aux-build:lint-stability.rs

#![allow(warnings)]

extern crate lint_stability;

use lint_stability::{unstable, deprecated};
//~^ ERROR use of unstable library feature `unstable_test_feature`

fn main() {
}
Correctly walk import lists in AST visitors 2015-09-12 16:10:12 +03:00			`// Unstable entities should be caught in import lists`

Moved and renamed ui issue tests. 2018-11-05 04:00:03 +00:00			`//@ aux-build:lint-stability.rs`
Don't use std in stability tests 2015-09-19 12:16:30 +03:00
rustc: Rearchitect lints to be emitted more eagerly In preparation for incremental compilation this commit refactors the lint handling infrastructure in the compiler to be more "eager" and overall more incremental-friendly. Many passes of the compiler can emit lints at various points but before this commit all lints were buffered in a table to be emitted at the very end of compilation. This commit changes these lints to be emitted immediately during compilation using pre-calculated lint level-related data structures. Linting today is split into two phases, one set of "early" lints run on the `syntax::ast` and a "late" set of lints run on the HIR. This commit moves the "early" lints to running as late as possible in compilation, just before HIR lowering. This notably means that we're catching resolve-related lints just before HIR lowering. The early linting remains a pass very similar to how it was before, maintaining context of the current lint level as it walks the tree. Post-HIR, however, linting is structured as a method on the `TyCtxt` which transitively executes a query to calculate lint levels. Each request to lint on a `TyCtxt` will query the entire crate's 'lint level data structure' and then go from there about whether the lint should be emitted or not. The query depends on the entire HIR crate but should be very quick to calculate (just a quick walk of the HIR) and the red-green system should notice that the lint level data structure rarely changes, and should hopefully preserve incrementality. Overall this resulted in a pretty big change to the test suite now that lints are emitted much earlier in compilation (on-demand vs only at the end). This in turn necessitated the addition of many `#![allow(warnings)]` directives throughout the compile-fail test suite and a number of updates to the UI test suite. 2017-07-26 21:51:09 -07:00			`#![allow(warnings)]`
Correctly walk import lists in AST visitors 2015-09-12 16:10:12 +03:00
Don't use std in stability tests 2015-09-19 12:16:30 +03:00			`extern crate lint_stability;`

Fix test/compile-fail 2018-07-23 12:22:23 +01:00			`use lint_stability::{unstable, deprecated};`
use backticks instead of single quotes when reporting "use of unstable library feature" This is consistent with all other diagnostics I could find containing features and enables the use of `DiagSymbolList` for generalizing diagnostics for unstable library features to multiple features. 2024-11-02 16:10:24 -07:00			//~^ ERROR use of unstable library feature `unstable_test_feature`
Correctly walk import lists in AST visitors 2015-09-12 16:10:12 +03:00
			`fn main() {`
			`}`