rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2025-07-10	cleaned up some tests	Kivooeo	-0/+2

2025-07-01	moved tests	Kivooeo	-0/+7

2025-06-02	Suppress redundant error	Michael Goulet	-12/+2

2025-06-02	Don't declare variables in ExprKind::Let in invalid positions	Michael Goulet	-0/+33

2025-02-21	More sophisticated span trimming	Michael Goulet	-3/+2

2025-02-10	Show diff suggestion format on verbose replacement	Esteban Küber	-10/+15
	``` error[E0610]: `{integer}` is a primitive type and therefore doesn't have fields --> $DIR/attempted-access-non-fatal.rs:7:15 \| LL \| let _ = 2.l; \| ^ \| help: if intended to be a floating point literal, consider adding a `0` after the period and a `f64` suffix \| LL - let _ = 2.l; LL + let _ = 2.0f64; \| ```
2024-12-09	Introduce `default_field_values` feature	Esteban Küber	-11/+11
	Initial implementation of `#[feature(default_field_values]`, proposed in https://github.com/rust-lang/rfcs/pull/3681. Support default fields in enum struct variant Allow default values in an enum struct variant definition: ```rust pub enum Bar { Foo { bar: S = S, baz: i32 = 42 + 3, } } ``` Allow using `..` without a base on an enum struct variant ```rust Bar::Foo { .. } ``` `#[derive(Default)]` doesn't account for these as it is still gating `#[default]` only being allowed on unit variants. Support `#[derive(Default)]` on enum struct variants with all defaulted fields ```rust pub enum Bar { #[default] Foo { bar: S = S, baz: i32 = 42 + 3, } } ``` Check for missing fields in typeck instead of mir_build. Expand test with `const` param case (needs `generic_const_exprs` enabled). Properly instantiate MIR const The following works: ```rust struct S<A> { a: Vec<A> = Vec::new(), } S::<i32> { .. } ``` Add lint for default fields that will always fail const-eval We allow this to happen for API writers that might want to rely on users' getting a compile error when using the default field, different to the error that they would get when the field isn't default. We could change this to always error instead of being a lint, if we wanted. This will not catch errors for partially evaluated consts, like when the expression relies on a const parameter. Suggestions when encountering `Foo { .. }` without `#[feature(default_field_values)]`: - Suggest adding a base expression if there are missing fields. - Suggest enabling the feature if all the missing fields have optional values. - Suggest removing `..` if there are no missing fields.
2024-11-23	Update tests for new TRPL chapter order	Chris Krycho	-1/+1

2024-10-24	add third help hint to diagnostic error E0027	Duncan Proctor	-0/+4

2024-02-16	[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives	许杰友 Jieyou Xu (Joe)	-8/+8

2024-01-09	Add error code for missing base expression in struct update syntax	clubby789	-3/+8

2023-12-08	Support bare unit structs in destructuring assignments	Michael Goulet	-11/+28

2023-11-24	Show number in error message even for one error	Nilstrieb	-1/+1
	Co-authored-by: Adrian <adrian.iosdev@gmail.com>
2023-07-17	add more tests	b-naber	-24/+3

2023-07-17	add test, bless tests	b-naber	-17/+40

2023-04-27	Provide RHS type hint when reporting operator error	Michael Goulet	-2/+2

2023-01-30	Modify primary span label for E0308	Esteban Küber	-1/+1
	The previous output was unintuitive to users.
2023-01-11	Move /src/test to /tests	Albert Larsan	-0/+680