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

Age	Commit message (Collapse)	Author	Lines
2023-01-11	Move /src/test to /tests	Albert Larsan	-9/+0

2023-01-08	Improve spans of non-WF implied bound types	Michael Goulet	-5/+3

2022-08-17	implied_bounds: clarify our assumptions	lcnr	-3/+5

2021-11-20	Point at source of trait bound obligations in more places	Esteban Kuber	-6/+0
	Be more thorough in using `ItemObligation` and `BindingObligation` when evaluating obligations so that we can point at trait bounds that introduced unfulfilled obligations. We no longer incorrectly point at unrelated trait bounds (`substs-ppaux.verbose.stderr`). In particular, we now point at trait bounds on method calls. We no longer point at "obvious" obligation sources (we no longer have a note pointing at `Trait` saying "required by a bound in `Trait`", like in `associated-types-no-suitable-supertrait*`). Address part of #89418.
2021-08-16	Use note to point at bound introducing requirement	Esteban Küber	-2/+5

2021-07-20	Support HIR wf checking for function signatures	Aaron Hill	-2/+5
	During function type-checking, we normalize any associated types in the function signature (argument types + return type), and then create WF obligations for each of the normalized types. The HIR wf code does not currently support this case, so any errors that we get have imprecise spans. This commit extends `ObligationCauseCode::WellFormed` to support recording a function parameter, allowing us to get the corresponding HIR type if an error occurs. Function typechecking is modified to pass this information during signature normalization and WF checking. The resulting code is fairly verbose, due to the fact that we can no longer normalize the entire signature with a single function call. As part of the refactoring, we now perform HIR-based WF checking for several other 'typed items' (statics, consts, and inherent impls). As a result, WF and projection errors in a function signature now have a precise span, which points directly at the responsible type. If a function signature is constructed via a macro, this will allow the error message to point at the code 'most responsible' for the error (e.g. a user-supplied macro argument).
2021-07-09	Replace associated item bound vars with placeholders when projecting.	jackh726	-5/+3

2019-03-11	Update tests	Vadim Petrochenkov	-1/+1

2018-12-25	Remove licenses	Mark Rousskov	-1/+1

2018-08-14	Merged migrated compile-fail tests and ui tests. Fixes #46841.	David Wood	-0/+11