rust-lang/rust
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
ead96f7f749846a2310e7aaedef0ea38fc7c3a4a
rust/src/test/ui/stability-attribute/stability-attribute-trait-impl.rs

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

30 lines
754 B
Rust
Raw Normal View History

Add test for unstable trait impl lint.
2020-09-10 20:55:04 +02:00
#![feature(staged_api)]
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 23:23:22 -04:00
//~^ ERROR module has missing stability attribute
Add test for unstable trait impl lint.
2020-09-10 20:55:04 +02:00
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 23:23:22 -04:00
#[stable(feature = "a", since = "1")]
Add test for unstable trait impl lint.
2020-09-10 20:55:04 +02:00
struct StableType;
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 23:23:22 -04:00
#[unstable(feature = "b", issue = "none")]
Add test for unstable trait impl lint.
2020-09-10 20:55:04 +02:00
struct UnstableType;
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 23:23:22 -04:00
#[stable(feature = "c", since = "1")]
Add test for unstable trait impl lint.
2020-09-10 20:55:04 +02:00
trait StableTrait {}
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 23:23:22 -04:00
#[unstable(feature = "d", issue = "none")]
Add test for unstable trait impl lint.
2020-09-10 20:55:04 +02:00
trait UnstableTrait {}
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 23:23:22 -04:00
#[unstable(feature = "e", issue = "none")]
Add test for unstable trait impl lint.
2020-09-10 20:55:04 +02:00
impl UnstableTrait for UnstableType {}
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 23:23:22 -04:00
#[unstable(feature = "f", issue = "none")]
Add test for unstable trait impl lint.
2020-09-10 20:55:04 +02:00
impl StableTrait for UnstableType {}
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 23:23:22 -04:00
#[unstable(feature = "g", issue = "none")]
Add test for unstable trait impl lint.
2020-09-10 20:55:04 +02:00
impl UnstableTrait for StableType {}
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 23:23:22 -04:00
#[unstable(feature = "h", issue = "none")]
Don't mark `ineffective_unstable_trait_impl` as an internal lint It's not an internal lint: - It's not in the rustc::internal lint group - It's on unconditionally, because it actually lints `staged_api`, not the compiler This fixes a bug where `#[deny(rustc::internal)]` would warn that `rustc::internal` was an unknown lint.
2021-01-15 15:21:20 -05:00
//~^ ERROR an `#[unstable]` annotation here has no effect [ineffective_unstable_trait_impl]
Add test for unstable trait impl lint.
2020-09-10 20:55:04 +02:00
impl StableTrait for StableType {}
fn main() {}
Reference in New Issue Copy Permalink