rust/tests/ui/lint/lint-output-format.rs

//@ compile-flags: -F unused_features
//@ aux-build:lint_output_format.rs

#![allow(deprecated)]

extern crate lint_output_format; //~ ERROR use of unstable library feature
use lint_output_format::{foo, bar}; //~ ERROR use of unstable library feature
//~| ERROR use of unstable library feature

fn main() {
    let _x = foo();
    let _y = bar(); //~ ERROR use of unstable library feature
}
Minor fixes 2015-01-16 22:08:24 +00:00			`//@ compile-flags: -F unused_features`
Add stability inheritance This commit makes several changes to the stability index infrastructure: * Stability levels are now inherited lexically, i.e., each item's stability level becomes the default for any nested items. * The computed stability level for an item is stored as part of the metadata. When using an item from an external crate, this data is looked up and cached. * The stability lint works from the computed stability level, rather than manual stability attribute annotations. However, the lint still checks only a limited set of item uses (e.g., it does not check every component of a path on import). This will be addressed in a later PR, as part of issue #8962. * The stability lint only applies to items originating from external crates, since the stability index is intended as a promise to downstream crates. * The "experimental" lint is now _allow_ by default. This is because almost all existing crates have been marked "experimental", pending library stabilization. With inheritance in place, this would generate a massive explosion of warnings for every Rust program. The lint should be changed back to deny-by-default after library stabilization is complete. * The "deprecated" lint still warns by default. The net result: we can begin tracking stability index for the standard libraries as we stabilize, without impacting most clients. Closes #13540. 2014-06-12 00:23:11 +00:00			`//@ aux-build:lint_output_format.rs`
Change default lint output format. Since lint check attributes are the preferred way of selectively enabling/disabling lint checks, the output format of a failed default check has been changed to reflect that. When lint checks are being explicitly set by a command-line flag or an attribute, the behavior is unchanged, so that the user can quickly pinpoint the source. Closes #6580 2013-10-09 01:26:09 +00:00
rustc: rework stability to be on-demand for type-directed lookup. 2016-11-10 17:08:21 +00:00			`#![allow(deprecated)]`
Minor fixes 2015-01-16 22:08:24 +00:00
Require feature attributes, and add them where necessary 2015-03-06 02:33:58 +00:00			`extern crate lint_output_format; //~ ERROR use of unstable library feature`
Correctly walk import lists in AST visitors 2015-09-12 13:10:12 +00:00			`use lint_output_format::{foo, bar}; //~ ERROR use of unstable library feature`
Correctly handle path stability for 'use tree' items PR #5956 started checking the stability of path segments. However, this was not applied to 'use tree' items (e.g. 'use some::path::{ItemOne, ItemTwo}') due to the way that we desugar these items in HIR lowering. This PR modifies 'use tree' lowering to preserve resolution information, which is needed by stability checking. 2022-07-15 17:22:36 +00:00			`//~\| ERROR use of unstable library feature`
Change default lint output format. Since lint check attributes are the preferred way of selectively enabling/disabling lint checks, the output format of a failed default check has been changed to reflect that. When lint checks are being explicitly set by a command-line flag or an attribute, the behavior is unchanged, so that the user can quickly pinpoint the source. Closes #6580 2013-10-09 01:26:09 +00:00
			`fn main() {`
rustc: rework stability to be on-demand for type-directed lookup. 2016-11-10 17:08:21 +00:00			`let _x = foo();`
Require feature attributes, and add them where necessary 2015-03-06 02:33:58 +00:00			`let _y = bar(); //~ ERROR use of unstable library feature`
Change default lint output format. Since lint check attributes are the preferred way of selectively enabling/disabling lint checks, the output format of a failed default check has been changed to reflect that. When lint checks are being explicitly set by a command-line flag or an attribute, the behavior is unchanged, so that the user can quickly pinpoint the source. Closes #6580 2013-10-09 01:26:09 +00:00			`}`