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

Age	Commit message (Collapse)	Author	Lines
2023-12-10	remove redundant imports	surechen	-2/+1
	detects redundant imports that can be eliminated. for #117772 : In order to facilitate review and modification, split the checking code and removing redundant imports code into two PR.
2023-12-07	recurse into refs when comparing tys for diagnostics	jyn	-14/+14

2023-10-25	Work around the fact that `check_mod_type_wf` may spuriously return ↵	Oli Scherer	-7/+25
	`ErrorGuaranteed`, even if that error is only emitted by `check_modwitem_types`
2023-08-26	More accurately point at arguments	Esteban Küber	-4/+2

2023-06-27	Don't sort strings right after we just sorted by types	Michael Goulet	-4/+4

2023-04-07	Use smart-resolve when checking for trait in RHS of UFCS	Michael Goulet	-95/+139

2023-04-02	Move some UI tests into subdirectories	jyn	-0/+154
	to avoid going over the existing limit now that the ui-fulldeps tests have been moved to ui.
2023-02-23	diagnostics: remove inconsistent English article "this" from E0107	Michael Howell	-2/+2
	Consider `tests/ui/const-generics/generic_const_exprs/issue-102768.stderr`, the error message where it gives additional notes about where the associated type is defined, and how the dead code lint doesn't have an article, like in `tests/ui/lint/dead-code/issue-85255.stderr`. They don't have articles, so it seems unnecessary to have one here.
2023-02-22	diagnostics: update test cases to refer to assoc fn with `self` as method	Michael Howell	-5/+5

2023-01-14	Rollup merge of #106752 - sulami:master, r=estebank	Matthias Krüger	-0/+14
	Emit a hint for bad call return types due to generic arguments When the return type of a function call depends on the type of an argument, e.g. ``` fn foo<T>(x: T) -> T { x } ``` and the expected type is set due to either an explicitly typed binding, or because the call to the function is in a tail position without semicolon, the current error implies that the argument in the call has the wrong type. This new hint highlights that the expected type doesn't match the returned type, which matches the argument type, and that that's why we're flagging the argument type. Fixes #43608.
2023-01-13	Emit a hint for bad call return types due to generic arguments	Robin Schroer	-0/+14
	When the return type of a function call depends on the type of an argument, e.g. ``` fn foo<T>(x: T) -> T { x } ``` and the expected type is set due to either an explicitly typed binding, or because the call to the function is in a tail position without semicolon, the current error implies that the argument in the call has the wrong type. This new hint highlights that the expected type doesn't match the returned type, which matches the argument type, and that that's why we're flagging the argument type. Fixes #43608.
2023-01-11	When suggesting writing a fully qualified path probe for appropriate types	Esteban Küber	-1/+6
	Fix #46585.
2023-01-11	Move /src/test to /tests	Albert Larsan	-0/+589