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

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

2022-06-03	Fully stabilize NLL	Jack Huey	-0/+13

2022-05-22	Use revisions for NLL in issues	Jack Huey	-32/+0

2021-10-13	Remove textual span from diagnostic string	Oli Scherer	-2/+2

2021-02-22	Update test cases	0yoyoyo	-3/+3

2020-08-22	Use smaller def span for functions	Aaron Hill	-4/+2
	Currently, the def span of a funtion encompasses the entire function signature and body. However, this is usually unnecessarily verbose - when we are pointing at an entire function in a diagnostic, we almost always want to point at the signature. The actual contents of the body tends to be irrelevant to the diagnostic we are emitting, and just takes up additional screen space. This commit changes the `def_span` of all function items (freestanding functions, `impl`-block methods, and `trait`-block methods) to be the span of the signature. For example, the function ```rust pub fn foo<T>(val: T) -> T { val } ``` now has a `def_span` corresponding to `pub fn foo<T>(val: T) -> T` (everything before the opening curly brace). Trait methods without a body have a `def_span` which includes the trailing semicolon. For example: ```rust trait Foo { fn bar(); }``` the function definition `Foo::bar` has a `def_span` of `fn bar();` This makes our diagnostic output much shorter, and emphasizes information that is relevant to whatever diagnostic we are reporting. We continue to use the full span (including the body) in a few of places: * MIR building uses the full span when building source scopes. * 'Outlives suggestions' use the full span to sort the diagnostics being emitted. * The `#[rustc_on_unimplemented(enclosing_scope="in this scope")]` attribute points the entire scope body. * The 'unconditional recursion' lint uses the full span to show additional context for the recursive call. All of these cases work only with local items, so we don't need to add anything extra to crate metadata.
2020-05-27	Tweak output for mismatched impl item	Esteban Küber	-1/+1
	Detect type parameter that might require lifetime constraint. Do not name `ReVar`s in expected/found output. Reword text suggesting to check the lifetimes.
2020-05-27	Name `RegionKind::ReVar` lifetimes in diagnostics	Esteban Küber	-1/+1

2020-05-27	Fix spacing of expected/found notes without a label	Esteban Küber	-2/+2

2019-12-03	Include a span in more `expected...found` notes	Aaron Hill	-3/+7
	In most places, we use a span when emitting `expected...found` errors. However, there were a couple of places where we didn't use any span, resulting in hard-to-interpret error messages. This commit attaches the relevant span to these notes, and additionally switches over to using `note_expected_found` instead of manually formatting the message
2019-10-11	Print lifetimes with backticks	Yuki Okushi	-1/+1

2019-10-07	update ui tests	Guillaume Gomez	-0/+1

2019-04-18	hide `--explain` hint if error has no extended info	Andy Russell	-1/+0

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

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

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