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

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

2022-12-30	Regression test for issue 106247	Gary Guo	-0/+9

2022-12-05	Point at GAT where clause when unsatisfied	Michael Goulet	-3/+3

2022-10-13	Sort elaborated existential predicates in object_ty_for_trait	Michael Goulet	-0/+25

2022-10-09	Elaborate trait ref to compute object safety.	Camille GILLOT	-0/+58

2022-10-07	Check WhereClauseReferencesSelf after all other object safety checks	Michael Goulet	-0/+46

2022-08-30	Tweak WellFormedLocs a bit	Michael Goulet	-18/+18

2022-08-18	Reword "Required because of the requirements on the impl of ..."	Andy Wang	-9/+9

2022-06-28	Migrate some rustc_borrowck diagnostics to SessionDiagnostic	Michael Goulet	-3/+3

2022-04-26	Move some tests to more reasonable places	Caio	-0/+57

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-09-15	Move object safety suggestions to the end of the error	Esteban Kuber	-10/+10

2021-08-11	Modify structured suggestion output	Esteban Küber	-16/+4
	* On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2020-10-20	review comments	Esteban Küber	-22/+22

2020-10-20	Tweak "object unsafe" errors	Esteban Küber	-91/+142
	Fix #77598.
2020-10-06	Check associated type bounds for object safety violations	Matthew Jasper	-0/+26

2020-09-02	pretty: trim paths of unique symbols	Dan Aloni	-9/+9
	If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not.
2020-02-03	Change wording for object unsafe because of assoc const	Esteban Küber	-2/+2

2020-02-02	Point at reason in object unsafe trait with `Self` in supertraits or ↵	Esteban Küber	-4/+10
	`where`-clause
2020-02-02	Use more appropriate spans on object unsafe traits and provide structured ↵	Esteban Küber	-6/+12
	suggestions when possible
2020-02-02	Wording changes to object unsafe trait errors	Esteban Küber	-18/+68
	Stemming from the thread at https://twitter.com/indygreg/status/1223279056398929920
2020-02-02	Slight rewording of diagnostic message	Esteban Küber	-4/+4

2020-02-02	Point at the `Sized` obligation in `where` clauses	Esteban Küber	-3/+6

2020-02-02	Tweak `Self: Sized` restriction diagnostic output	Esteban Küber	-3/+0

2020-02-02	Point at `Sized` bound	Esteban Küber	-0/+6

2020-02-02	Point at arguments or output when fn obligations come from them, or ident ↵	Esteban Küber	-16/+16
	when they don't
2019-10-22	RFC 2027: "first draft" of implementation	Mathias Blikstad	-25/+183
	These are a squashed series of commits.
2019-09-02	account for DUMMY_SP and correct wording	Esteban Küber	-2/+2

2019-09-02	On object safety violation, point at source when possible	Esteban Küber	-12/+18

2019-09-02	Refer to "`self` type" instead of "receiver type"	Esteban Küber	-1/+1

2019-07-03	Migrate compile-pass annotations to build-pass	Yuki Okushi	-2/+2

2019-05-29	Update ui test suite to use dyn	memoryruins	-52/+52

2019-04-22	update tests for migrate mode by default	Matthew Jasper	-11/+2

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

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

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

2018-11-07	Removed `#[rustc_error]` from tests that are all `// compile-pass`.	Felix S. Klock II	-24/+6
	I also added `// skip-codegen` to each one, to address potential concerns that this change would otherwise slow down our test suite spending time generating code for files that are really just meant to be checks of compiler diagnostics. (However, I will say: My preference is to not use `// skip-codegen` if one can avoid it. We can use all the testing of how we drive LLVM that we can get...) (Updated post rebase.)
2018-08-14	Merged migrated compile-fail tests and ui tests. Fixes #46841.	David Wood	-0/+527