about summary refs log tree commit diff
path: root/tests/ui/stability-attribute/const-stability-attribute-implies-no-feature.stderr
AgeCommit message (Collapse)AuthorLines
2025-01-18Structured suggestion for "missing `feature` in unstable fn call"Esteban Küber-1/+4
When encountering a call corresponding to an item marked as unstable behind a feature flag, provide a structured suggestion pointing at where in the crate the `#![feature(..)]` needs to be written. ``` error: `foobar` is not yet stable as a const fn --> $DIR/const-stability-attribute-implies-no-feature.rs:12:5 | LL | foobar(); | ^^^^^^^^ | help: add `#![feature(const_foobar)]` to the crate attributes to enable | LL + #![feature(const_foobar)] | ``` Fix #81370.
2023-11-24Show number in error message even for one errorNilstrieb-1/+1
Co-authored-by: Adrian <adrian.iosdev@gmail.com>
2023-02-08const_eval: `implies_by` in `rustc_const_unstable`David Wood-0/+10
Extend support for `implies_by` (from `#[stable]` and `#[unstable]`) to `#[rustc_const_stable]` and `#[rustc_const_unstable]`. Signed-off-by: David Wood <david.wood@huawei.com>