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

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

2022-12-13	Stop pointing to operators if their libcore method source is not available	Oli Scherer	-12/+2

2022-12-13	Make some diagnostics not depend on the source of what they reference being ↵	Oli Scherer	-6/+10
	available
2022-11-23	Suggest `.clone()` or `ref binding` on E0382	Esteban Küber	-0/+4

2022-06-28	Remove redundant logic to suggest `as_ref`	Michael Goulet	-2/+14

2021-09-25	Use larger span for adjustments on method calls	Aaron Hill	-1/+1
	Currently, we use a relatively 'small' span for THIR expressions generated by an 'adjustment' (e.g. an autoderef, autoborrow, unsizing). As a result, if a borrow generated by an adustment ends up causing a borrowcheck error, for example: ```rust let mut my_var = String::new(); let my_ref = &my_var my_var.push('a'); my_ref; ``` then the span for the mutable borrow may end up referring to only the base expression (e.g. `my_var`), rather than the method call which triggered the mutable borrow (e.g. `my_var.push('a')`) Due to a quirk of the MIR borrowck implementation, this doesn't always get exposed in migration mode, but it does in many cases. This commit makes THIR building consistently use 'larger' spans for adjustment expressions The intent of this change it make it clearer to users when it's the specific way in which a variable is used (for example, in a method call) that produdes a borrowcheck error. For example, an error message claiming that a 'mutable borrow occurs here' might be confusing if it just points at a usage of a variable (e.g. `my_var`), when no `&mut` is in sight. Pointing at the entire expression should help to emphasize that the method call itself is responsible for the mutable borrow. In several cases, this makes the `#![feature(nll)]` diagnostic output match up exactly with the default (migration mode) output. As a result, several `.nll.stderr` files end up getting removed entirely.
2021-08-11	Modify structured suggestion output	Esteban Küber	-2/+2
	* On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2020-07-27	mv std libs to library/	mark	-1/+1

2020-06-26	Explain move errors that occur due to method calls involving `self`	Aaron Hill	-7/+14
	This is a re-attempt of #72389 (which was reverted in #73594) Instead of using `ExpnKind::Desugaring` to represent operators, this PR checks the lang item directly.
2020-06-22	Revert "Rollup merge of #72389 - Aaron1011:feature/move-fn-self-msg, ↵	Aaron Hill	-14/+7
	r=nikomatsakis" This reverts commit 372cb9b69c76a042d0b9d4b48ff6084f64c84a2c, reversing changes made to 5c61a8dc34c3e2fc6d7f02cb288c350f0233f944.
2020-06-11	Explain move errors that occur due to method calls involving `self`	Aaron Hill	-7/+14

2020-03-29	Tweak `suggest_constraining_type_param`	Esteban Küber	-8/+6
	Some of the bound restriction structured suggestions were incorrect while others had subpar output.
2020-02-09	Improve reporting errors and suggestions for trait bounds	Patryk Wychowaniec	-6/+14

2019-11-28	Deduplicate type param constraint suggestion code	Esteban Küber	-2/+2

2019-11-28	Use structured suggestion when requiring `Copy` constraint in type param	Esteban Küber	-4/+4

2019-06-03	Update tests for changes to cannot move errors	Matthew Jasper	-4/+4

2019-04-22	update tests for migrate mode by default	Matthew Jasper	-26/+41

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

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

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

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