mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e30d27be00
rust/tests/ui/stability-attribute/stability-attribute-trait-impl.stderr

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

32 lines
999 B
Plaintext
Raw Normal View History

Improve `ineffective_unstable_trait_impl` error message.
2020-09-11 14:42:28 -05:00
error: an `#[unstable]` annotation here has no effect
Add test.
2022-10-19 05:41:56 -05:00
--> $DIR/stability-attribute-trait-impl.rs:32:1
Add test for unstable trait impl lint.
2020-09-10 13:55:04 -05:00
|
Add test.
2022-10-19 05:41:56 -05:00
LL | #[unstable(feature = "j", issue = "none")]
Add test for unstable trait impl lint.
2020-09-10 13:55:04 -05:00
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
Improve `ineffective_unstable_trait_impl` error message.
2020-09-11 14:42:28 -05:00
= note: see issue #55436 <https://github.com/rust-lang/rust/issues/55436> for more information
bless ui tests
2022-09-18 10:55:36 -05:00
= note: `#[deny(ineffective_unstable_trait_impl)]` on by default
Add test for unstable trait impl lint.
2020-09-10 13:55:04 -05:00
Add test for #[unstable] impl for fn() -> !.
2022-10-19 06:25:37 -05:00
error: an `#[unstable]` annotation here has no effect
--> $DIR/stability-attribute-trait-impl.rs:36:1
|
LL | #[unstable(feature = "k", issue = "none")]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #55436 <https://github.com/rust-lang/rust/issues/55436> for more information
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
--> $DIR/stability-attribute-trait-impl.rs:1:1
|
Update tests
2022-12-23 01:50:05 -06:00
LL | / #![feature(staged_api, never_type, rust_cold_cc)]
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
LL | |
LL | |
LL | | #[stable(feature = "a", since = "1")]
... |
LL | |
LL | | fn main() {}
| |____________^
Add test for #[unstable] impl for fn() -> !.
2022-10-19 06:25:37 -05:00
error: aborting due to 3 previous errors
Add test for unstable trait impl lint.
2020-09-10 13:55:04 -05:00
Reference in New Issue Copy Permalink