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

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

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

2022-06-02	add new `emit_inference_failure_err`	lcnr	-4/+7

2021-11-21	Simplify for loop desugar	Cameron Steffen	-2/+4

2021-11-20	Do not mention associated items when they introduce an obligation	Esteban Kuber	-12/+0

2021-07-19	Various diagnostics clean ups/tweaks	Esteban Küber	-2/+10
	* Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition
2020-10-06	Fix tests from rebase	Matthew Jasper	-3/+5

2020-10-06	Fix tests and bootstrap	Matthew Jasper	-9/+11

2020-09-02	pretty: trim paths of unique symbols	Dan Aloni	-6/+6
	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-06-26	Show the values and computation that would overflow a const evaluation or ↵	Oliver Scherer	-2/+2
	propagation
2020-06-13	Prefer the associated consts for pattern matching error	Lzu Tao	-2/+2

2020-03-27	non-exhastive diagnostic: add note re. scrutinee type	Mazdak Farrokhzad	-0/+2

2020-02-17	Do not emit note suggesting to implement trait to foreign type	LeSeulArtichaut	-2/+0
	Update tests Extend to other operations Refractor check in a separate function Fix more tests
2019-12-12	Update tests	LeSeulArtichaut	-1/+1

2019-12-12	Update UI test expectations	LeSeulArtichaut	-1/+1

2019-09-19	When possible point at argument causing item obligation failure	Esteban Küber	-0/+3

2019-09-15	use println!()	Guanqun Lu	-1/+1

2019-09-09	check_match: unify check_irrefutable & check_exhaustive more.	Mazdak Farrokhzad	-2/+2

2019-08-13	Suggest giving return type to closures on E0282	Esteban Küber	-4/+1

2019-08-06	pretty-pretty extremal constants!	Zack M. Davis	-2/+2
	While many programmers may intuitively appreciate the significance of "magic numbers" like −2147483648, Rust is about empowering everyone to build reliable and efficient software! It's a bit more legible to print the constant names (even noisy fully-qualified-paths thereof). The bit-manipulation methods mirror those in `librustc_mir::hair::pattern::_match::all_constructors`; thanks to the immortal Varkor for guidance. Resolves #56393.
2019-03-27	Better diagnostic for binary operation on BoxedValues	hgallagher1993	-2/+4

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

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

2018-11-30	Update existing tests with more precise error messages	varkor	-2/+2

2018-10-09	Reword `rustc_on_unimplemented` errors for `Iterator`	Esteban Küber	-6/+7
	- Detect one element array of `Range` type, which is potentially a typo: `for _ in [0..10] {}` where iterating between `0` and `10` was intended. (#23141) - Suggest `.bytes()` and `.chars()` for `String`. - Suggest borrowing or `.iter()` on arrays (#36391) - Suggest using range literal when iterating on integers (#34353) - Do not suggest `.iter()` by default (#50773, #46806)
2018-08-14	Merged migrated compile-fail tests and ui tests. Fixes #46841.	David Wood	-0/+183