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

Age	Commit message (Collapse)	Author	Lines
2021-08-25	Adjust spans	Noah Lev	-4/+4
	* Highlight the whole pattern if it has no fields * Highlight the whole definition if it has no fields * Only highlight the pattern name if the pattern is multi-line * Determine whether a pattern is multi-line based on distance from name to last field, rather than first field
2021-08-21	Make E0023 spans even more precise	Noah Lev	-20/+12

2021-08-17	Make spans for tuple patterns in E0023 more precise	Noah Lev	-8/+16
	As suggested in #86307.
2021-08-11	Modify structured suggestion output	Esteban Küber	-6/+6
	* On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-04-17	Move some tests to more reasonable directories - 6	Caio	-0/+78

2021-01-26	Tweak suggestion for missing field in patterns	Esteban Küber	-4/+4
	Account for parser recovered struct and tuple patterns to avoid invalid suggestion. Follow up to #81103.
2021-01-16	don't suggest erroneous trailing comma after `..`	Zack M. Davis	-2/+2
	In #76612, suggestions were added for missing fields in patterns. However, the suggestions are being inserted just at the end of the last field in the pattern—before any trailing comma after the last field. This resulted in the "if you don't care about missing fields" suggestion to recommend code with a trailing comma after the field ellipsis (`..,`), which is actually not legal ("`..` must be at the end and cannot have a trailing comma")! Incidentally, the doc-comment on `error_unmentioned_fields` was using `you_cant_use_this_field` as an example field name (presumably copy-paste inherited from the description of Issue #76077), but the present author found this confusing, because unmentioned fields aren't necessarily unusable. The suggested code in the diff this commit introduces to `destructuring-assignment/struct_destructure_fail.stderr` doesn't work, but it didn't work beforehand, either (because of the "found reserved identifier `_`" thing), so you can't really call it a regression; it could be fixed in a separate PR. Resolves #78511.
2021-01-12	Include `..` suggestion if fields are all wildcards	Camelid	-0/+8

2021-01-12	Always show suggestions in their own subwindows	Camelid	-8/+12

2021-01-12	Only suggest `..` if more than one field is missing	Camelid	-20/+8

2021-01-12	Specialize `..` help message for all fields vs. the rest	Camelid	-2/+2

2021-01-12	Suggest `Variant(..)` if all of the mentioned fields are `_`	Camelid	-4/+4

2021-01-12	Suggest `_` and `..` if a pattern has too few fields	Camelid	-0/+18
	For example, this code: struct S(i32, f32); let S(x) = S(0, 1.0); will make the compiler suggest either: let S(x, _) = S(0, 1.0); or: let S(x, ..) = S(0, 1.0);
2020-11-18	Test drop order for (destructuring) assignments	Fabian Zaiser	-0/+44

2020-11-14	Add underscore expressions for destructuring assignments	Fabian Zaiser	-16/+105
	Co-authored-by: varkor <github@varkor.com>
2020-11-11	Implement destructuring assignment for structs and slices	Fabian Zaiser	-30/+315
	Co-authored-by: varkor <github@varkor.com>
2020-11-07	Implement destructuring assignment for tuples	Fabian Zaiser	-39/+159
	Co-authored-by: varkor <github@varkor.com>
2020-02-17	Do not emit note suggesting to implement trait to foreign type	LeSeulArtichaut	-4/+0
	Update tests Extend to other operations Refractor check in a separate function Fix more tests
2019-12-23	Add new folder for destructuring assignment tests	varkor	-0/+147