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

Age	Commit message (Collapse)	Author	Lines
2025-02-15	Use `clippy_utils::is_mutable()` in `unnecessary_struct_initialization`	Samuel Tardieu	-12/+2

2024-12-15	Merge remote-tracking branch 'upstream/master' into rustup	Philipp Krones	-2/+4

2024-12-09	Introduce `default_field_values` feature	Esteban Küber	-4/+4
	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-07-25	Merge commit '37f4fbb92913586b73a35772efd00eccd1cbbe13' into ↵	Philipp Krones	-36/+151
	clippy-subtree-update
2024-07-09	unnecessary_struct_initialization: extend to assignments moving all fields	Philipp Gesang	-36/+151
	This lint makes Clippy warn about situations where an owned struct is essentially recreated by moving all its fields into a new instance of the struct. Until now this lint only triggered for structs recreated from a base struct. NB: The new functionality too will cause false positives for the situation where a non-copy struct consisting of all copy members is touched again in subsequent code.
2024-04-17	Rename `BindingAnnotation` to `BindingMode`	Jules Bertholet	-2/+2

2023-12-12	Move some methods from `tcx.hir()` to `tcx`	zetanumbers	-1/+1
	Renamings: - find -> opt_hir_node - get -> hir_node - find_by_def_id -> opt_hir_node_by_def_id - get_by_def_id -> hir_node_by_def_id Fix rebase changes using removed methods Use `tcx.hir_node_by_def_id()` whenever possible in compiler Fix clippy errors Fix compiler Apply suggestions from code review Co-authored-by: Vadim Petrochenkov <vadim.petrochenkov@gmail.com> Add FIXME for `tcx.hir()` returned type about its removal Simplify with with `tcx.hir_node_by_def_id`
2023-12-01	Merge commit 'f0cdee4a3f094416189261481eae374b76792af1' into clippy-subtree-sync	Philipp Krones	-1/+1

2023-11-02	Merge commit '09ac14c901abc43bd0d617ae4a44e8a4fed98d9c' into clippyup	Philipp Krones	-10/+10

2023-07-17	Merge commit 'd9c24d1b1ee61f276e550b967409c9f155eac4e3' into clippyup	Philipp Krones	-1/+4

2023-04-11	Merge commit '83e42a2337dadac915c956d125f1d69132f36425' into clippyup	Philipp Krones	-2/+6

2023-03-24	Merge commit 'd5e2a7aca55ed49fc943b7a07a8eba05ab5a0079' into clippyup	Philipp Krones	-0/+84