rust/tests/ui/stability-attribute/stability-attribute-implies-using-unstable.stderr

error: the feature `foo` has been partially stabilized since 1.62.0 and is succeeded by the feature `foobar`
  --> $DIR/stability-attribute-implies-using-unstable.rs:3:12
   |
LL | #![feature(foo)]
   |            ^^^
   |
note: the lint level is defined here
  --> $DIR/stability-attribute-implies-using-unstable.rs:2:9
   |
LL | #![deny(stable_features)]
   |         ^^^^^^^^^^^^^^^
help: if you are using features which are still unstable, change to using `foobar`
   |
LL | #![feature(foobar)]
   |            ~~~~~~
help: if you are using features which are now stable, remove this line
   |
LL - #![feature(foo)]
   |

error: aborting due to 1 previous error
passes: improved partial stabilization diagnostic Improves the diagnostic when a feature attribute is specified unnecessarily but the feature implies another (i.e. it was partially stabilized) to refer to the implied feature. Signed-off-by: David Wood <david.wood@huawei.com> 2022-07-13 09:10:19 -05:00			error: the feature `foo` has been partially stabilized since 1.62.0 and is succeeded by the feature `foobar`
middle: add `implies_by` to `#[unstable]` If part of a feature is stabilized and a new feature is added for the remaining parts, then the `implied_by` attribute can be used to indicate which now-stable feature previously contained a item. If the now-stable feature is still active (if the user has only just updated rustc, for example) then there will not be an stability error for uses of the item from the implied feature. Signed-off-by: David Wood <david.wood@huawei.com> 2022-07-13 07:10:37 -05:00			`--> $DIR/stability-attribute-implies-using-unstable.rs:3:12`
			`\|`
			`LL \| #![feature(foo)]`
			`\| ^^^`
			`\|`
			`note: the lint level is defined here`
			`--> $DIR/stability-attribute-implies-using-unstable.rs:2:9`
			`\|`
			`LL \| #![deny(stable_features)]`
			`\| ^^^^^^^^^^^^^^^`
passes: improved partial stabilization diagnostic Improves the diagnostic when a feature attribute is specified unnecessarily but the feature implies another (i.e. it was partially stabilized) to refer to the implied feature. Signed-off-by: David Wood <david.wood@huawei.com> 2022-07-13 09:10:19 -05:00			help: if you are using features which are still unstable, change to using `foobar`
			`\|`
			`LL \| #![feature(foobar)]`
			`\| ~~~~~~`
			`help: if you are using features which are now stable, remove this line`
			`\|`
			`LL - #![feature(foo)]`
			`\|`
middle: add `implies_by` to `#[unstable]` If part of a feature is stabilized and a new feature is added for the remaining parts, then the `implied_by` attribute can be used to indicate which now-stable feature previously contained a item. If the now-stable feature is still active (if the user has only just updated rustc, for example) then there will not be an stability error for uses of the item from the implied feature. Signed-off-by: David Wood <david.wood@huawei.com> 2022-07-13 07:10:37 -05:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
middle: add `implies_by` to `#[unstable]` If part of a feature is stabilized and a new feature is added for the remaining parts, then the `implied_by` attribute can be used to indicate which now-stable feature previously contained a item. If the now-stable feature is still active (if the user has only just updated rustc, for example) then there will not be an stability error for uses of the item from the implied feature. Signed-off-by: David Wood <david.wood@huawei.com> 2022-07-13 07:10:37 -05:00