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

Age	Commit message (Collapse)	Author	Lines
2021-02-17	Rollup merge of #79981 - camelid:overflowing_literals-inference-error, r=lcnr	Guillaume Gomez	-0/+4
	Add 'consider using' message to overflowing_literals Fixes #79744. Ironically, the `overflowing_literals` handler for binary or hex already had this message! You would think it would be the other way around :) cc ```@scottmcm```
2021-02-13	Improve error and help messages	Camelid	-4/+4

2020-12-26	update tests	Bastian Kauschke	-32/+29

2020-12-12	Add 'consider using' message to overflowing_literals	Camelid	-0/+4
	Ironically, the overflowing_literals handler for binary or hex already had this message! You would think it would be the other way around :)
2020-05-07	Add some tests for #67945	Yuki Okushi	-0/+59

2020-04-11	rustc: Add a warning count upon completion	RoccoDev	-0/+2

2020-03-15	Add more context to the literal overflow message	YI	-0/+7

2020-01-24	Normalise notes with the/is	varkor	-2/+2

2019-12-06	accept union inside enum if not followed by identifier	Kamlesh Kumar	-0/+13

2019-11-23	Add error reporting on nested keywords inside 'enum' definition	Janusz Marcinkiewicz	-0/+34

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

2019-04-30	Place types inside backticks	varkor	-8/+8

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

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

2018-12-25	Remove licenses	Mark Rousskov	-110/+19

2018-12-25	Auto merge of #57088 - euclio:non-camel-case-early-lint, r=estebank	bors	-1/+3
	make non_camel_case_types an early lint This allows us to catch these kinds of style violations much earlier, as evidenced by the large number of tests that had to be updated for this change.
2018-12-24	make non_camel_case_types an early lint	Andy Russell	-1/+3

2018-12-22	enum type instead of variant suggestion unification	Zack M. Davis	-1/+1
	Weirdly, we were deciding between a help note and a structured suggestion based on whether the import candidate span was a dummy—but we weren't using that span in any case! The dummy-ness of the span (which appears to be a matter of this-crate vs. other-crate definition) isn't the right criterion by which we should decide whether it's germane to mention that "there is an enum variant"; instead, let's use the someness of `def` (which is used as the `has_unexpected_resolution` argument to `error_code`). Since `import_candidate_to_paths` has no other callers, we are free to stop returning the span and rename the function. By using `span_suggestions_`, we leverage the max-suggestions output limit already built in to the emitter, thus resolving #56028. In the matter of message wording, "you can" is redundant (and perhaps too informal); prefer the imperative.
2018-11-18	resolve: Tweak some articles in ambiguity diagnostics	Vadim Petrochenkov	-1/+1

2018-08-31	cleanup: Add main functions to some UI tests	Vadim Petrochenkov	-7/+3

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