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

Age	Commit message (Collapse)	Author	Lines
2024-10-28	Tweak more warnings.	Nicholas Nethercote	-4/+4
	Much like the previous commit. I think the removal of "the token" in each message is fine here. There are many more error messages that mention tokens without saying "the token" than those that do say it.
2024-10-28	Tweak `expand_incomplete_parse` warning.	Nicholas Nethercote	-8/+8
	By using `token_descr`, as is done for many other errors, we can get slightly better descriptions in error messages, e.g. "macro expansion ignores token `let` and any following" becomes "macro expansion ignores keyword `let` and any tokens following". This will be more important once invisible delimiters start being mentioned in error messages -- without this commit, that leads to error messages such as "error at ``" because invisible delimiters are pretty printed as an empty string.
2024-07-24	Mark `missing_fragment_specifier` as `FutureReleaseErrorReportInDeps`	Trevor Gross	-0/+11
	We are moving toward forbidding `missing_fragment_specifier` either in edition 2024 or unconditionally. Make a first step toward this by ensuring crates that rely on the old behavior are reported when used as dependencies. Tracking issue: <https://github.com/rust-lang/rust/issues/128143>
2024-07-12	Make parse error suggestions verbose and fix spans	Esteban Küber	-1/+6
	Go over all structured parser suggestions and make them verbose style. When suggesting to add or remove delimiters, turn them into multiple suggestion parts.
2024-06-03	Spruce up the diagnostics of some early lints	León Orell Valerian Liehr	-2/+2

2024-06-01	Reject CVarArgs in parse_ty_for_where_clause	León Orell Valerian Liehr	-0/+11

2024-05-11	Add parser tests for statement boundary insertion	David Tolnay	-0/+104

2024-02-16	[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives	许杰友 Jieyou Xu (Joe)	-3/+3

2023-12-27	Introduce `const Trait` (always-const trait bounds)	León Orell Valerian Liehr	-0/+16

2023-12-03	Disallow an arm without a body (except for never patterns)	Nadrieril	-1/+8
	Parsing now accepts a match arm without a body, so we must make sure to only accept that if the pattern is a never pattern.
2023-12-03	Detect attempts to expand a macro to a match arm again	Nadrieril	-0/+2
	Because a macro invocation can expand to a never pattern, we can't rule out a `arm!(),` arm at parse time. Instead we detect that case at expansion time, if the macro tries to output a pattern followed by `=>`.
2023-12-03	Parse a pattern with no arm	Nadrieril	-7/+10

2023-11-24	Show number in error message even for one error	Nilstrieb	-6/+6
	Co-authored-by: Adrian <adrian.iosdev@gmail.com>
2023-10-05	Add a note to duplicate diagnostics	Alex Macleod	-0/+2

2023-08-21	discard dummy field for macro invocation when parse struct	bohan	-38/+44

2023-08-02	Add test for enum with fields	Catherine Flores	-31/+53

2023-07-24	Recover from some macros	Catherine Flores	-86/+88

2023-07-24	Specify macro is invalid in certain contexts	Catherine	-0/+148

2023-01-11	Move /src/test to /tests	Albert Larsan	-0/+393