mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
be413ae527
rust/tests/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.

44 lines
1.2 KiB
Rust
Raw Normal View History

Add test.
2022-10-19 05:41:56 -05:00
#![feature(staged_api, never_type, c_unwind)]
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 22:23:22 -05:00
//~^ ERROR module has missing stability attribute
Add test for unstable trait impl lint.
2020-09-10 13:55:04 -05: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 22:23:22 -05:00
#[stable(feature = "a", since = "1")]
Add test for unstable trait impl lint.
2020-09-10 13:55:04 -05: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 22:23:22 -05:00
#[unstable(feature = "b", issue = "none")]
Add test for unstable trait impl lint.
2020-09-10 13:55:04 -05: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 22:23:22 -05:00
#[stable(feature = "c", since = "1")]
Add test for unstable trait impl lint.
2020-09-10 13:55:04 -05: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 22:23:22 -05:00
#[unstable(feature = "d", issue = "none")]
Add test for unstable trait impl lint.
2020-09-10 13:55:04 -05: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 22:23:22 -05:00
#[unstable(feature = "e", issue = "none")]
Add test for unstable trait impl lint.
2020-09-10 13:55:04 -05: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 22:23:22 -05:00
#[unstable(feature = "f", issue = "none")]
Add test for unstable trait impl lint.
2020-09-10 13:55:04 -05: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 22:23:22 -05:00
#[unstable(feature = "g", issue = "none")]
Add test for unstable trait impl lint.
2020-09-10 13:55:04 -05: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 22:23:22 -05:00
#[unstable(feature = "h", issue = "none")]
Add test.
2022-10-19 05:41:56 -05:00
impl StableTrait for ! {}
// Note: If C-unwind is stabilized, switch this to another (unstable) ABI.
#[unstable(feature = "i", issue = "none")]
impl StableTrait for extern "C-unwind" fn() {}
#[unstable(feature = "j", 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 14:21:20 -06:00
//~^ ERROR an `#[unstable]` annotation here has no effect [ineffective_unstable_trait_impl]
Add test for unstable trait impl lint.
2020-09-10 13:55:04 -05:00
impl StableTrait for StableType {}
Add test for #[unstable] impl for fn() -> !.
2022-10-19 06:25:37 -05:00
#[unstable(feature = "k", issue = "none")]
//~^ ERROR an `#[unstable]` annotation here has no effect [ineffective_unstable_trait_impl]
impl StableTrait for fn() -> ! {}
Allow #[unstable] impl for fn() -> UnstableType. (But not fn() -> !, which is stable.)
2022-10-19 06:33:45 -05:00
#[unstable(feature = "l", issue = "none")]
impl StableTrait for fn() -> UnstableType {}
Add test for unstable trait impl lint.
2020-09-10 13:55:04 -05:00
fn main() {}
Reference in New Issue Copy Permalink