Matthias Krüger 7edd17cfbb Rollup merge of #135711 - estebank:issue-135649, r=davidtwco ... Do not ICE on default_field_value const with lifetimes `#![feature(default_field_values)]` uses a `const` body that should be treated as inline `const`s, but is actually being detected otherwise. This is similar to the situation in #78174, so we take the same solution: we check if the const actually comes from a field, and if it does, we use that logic to get the appropriate lifetimes and not ICE during borrowck. Fix #135649.		2025-02-18 18:40:49 +01:00
..
auxiliary
do-not-ice-on-invalid-lifetime.rs	Do not ICE on default_field_value const with lifetimes	2025-01-18 23:40:34 +00:00
do-not-ice-on-invalid-lifetime.stderr	Do not ICE on default_field_value const with lifetimes	2025-01-18 23:40:34 +00:00
empty-struct.rs	Disallow A { .. } if A has no fields	2025-01-18 21:05:09 +00:00
empty-struct.stderr	Disallow A { .. } if A has no fields	2025-01-18 21:05:09 +00:00
failures.rs
failures.stderr
invalid-const.rs
invalid-const.stderr
non-exhaustive-ctor.disabled.stderr	Show diff suggestion format on verbose replacement	2025-02-10 20:21:39 +00:00
non-exhaustive-ctor.enabled.fixed	Detect missing fields with default values and suggest ..	2025-01-21 21:26:37 +00:00
non-exhaustive-ctor.enabled.stderr	Show diff suggestion format on verbose replacement	2025-02-10 20:21:39 +00:00
non-exhaustive-ctor.rs	Detect missing fields with default values and suggest ..	2025-01-21 21:26:37 +00:00
support.rs
use-normalized-ty-for-default-struct-value.rs	Make sure to use normalized ty for unevaluated const for default struct value	2024-12-14 18:05:19 +00:00
visibility.rs	Emit a single privacy error for multiple fields on the same struct expression	2025-01-18 20:33:15 +00:00
visibility.stderr	Emit a single privacy error for multiple fields on the same struct expression	2025-01-18 20:33:15 +00:00