os-rust/tests/ui/stability-attribute/stability-attribute-sanity-3.rs

// More checks that stability attributes are used correctly

#![feature(staged_api)]

#![stable(feature = "stable_test_feature", since = "1.0.0")]

#[macro_export]
macro_rules! mac { //~ ERROR macro has missing stability attribute
    () => ()
}

fn main() { }
rustc: rework stability to be on-demand for type-directed lookup. 2016-11-10 19:08:21 +02:00			`// More checks that stability attributes are used correctly`
Add autogenerated tests for the spans of various derived traits. 2014-01-27 15:28:04 +11:00
rustc: rework stability to be on-demand for type-directed lookup. 2016-11-10 19:08:21 +02:00			`#![feature(staged_api)]`
Add autogenerated tests for the spans of various derived traits. 2014-01-27 15:28:04 +11:00
Fix test/compile-fail 2018-07-23 12:22:23 +01:00			`#![stable(feature = "stable_test_feature", since = "1.0.0")]`
syntax::ext: Make type errors in deriving point to the field itself. This rearranges the deriving code so that #[deriving] a trait on a field that doesn't implement that trait will point to the field in question, e.g. struct NotEq; // doesn't implement Eq #[deriving(Eq)] struct Foo { ok: int, also_ok: ~str, bad: NotEq // error points here. } Unfortunately, this means the error is disconnected from the `deriving` itself but there's no current way to pass that information through to rustc except via the spans, at the moment. Fixes #7724. 2013-11-07 18:49:01 +11:00
rustc: rework stability to be on-demand for type-directed lookup. 2016-11-10 19:08:21 +02:00			`#[macro_export]`
Improve the error messages for missing stability attributes This makes the capitalisation consistent and provides more context (especially for missing top-level attributes). 2019-02-07 16:38:23 +01:00			`macro_rules! mac { //~ ERROR macro has missing stability attribute`
rustc: rework stability to be on-demand for type-directed lookup. 2016-11-10 19:08:21 +02:00			`() => ()`
syntax::ext: Make type errors in deriving point to the field itself. This rearranges the deriving code so that #[deriving] a trait on a field that doesn't implement that trait will point to the field in question, e.g. struct NotEq; // doesn't implement Eq #[deriving(Eq)] struct Foo { ok: int, also_ok: ~str, bad: NotEq // error points here. } Unfortunately, this means the error is disconnected from the `deriving` itself but there's no current way to pass that information through to rustc except via the spans, at the moment. Fixes #7724. 2013-11-07 18:49:01 +11:00			`}`

rustc: rework stability to be on-demand for type-directed lookup. 2016-11-10 19:08:21 +02:00			`fn main() { }`