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

Age	Commit message (Collapse)	Author	Lines
2022-08-25	Separate CountIsStar from CountIsParam in rustc_parse_format.	Mara Bos	-2/+4

2022-08-21	Fix rustc_parse_format precision & width spans	Alex Macleod	-54/+68

2022-08-18	Add diagnostic translation lints to crates that don't emit them	5225225	-0/+2

2022-08-04	add a comment about what we can parse now	Takayuki Maeda	-0/+2

2022-08-04	return when captured argument is not a struct field	Takayuki Maeda	-13/+12

2022-08-03	suggest a positional formatting argument instead of a captured argument	Takayuki Maeda	-7/+41

2022-07-31	Always include a position span in rustc_parse_format::Argument	Alex Macleod	-29/+81

2022-07-25	Generate correct suggestion with named arguments used positionally	Preston From	-12/+36
	Address issue #99265 by checking each positionally used argument to see if the argument is named and adding a lint to use the name instead. This way, when named arguments are used positionally in a different order than their argument order, the suggested lint is correct. For example: ``` println!("{b} {}", a=1, b=2); ``` This will now generate the suggestion: ``` println!("{b} {a}", a=1, b=2); ``` Additionally, this check now also correctly replaces or inserts only where the positional argument is (or would be if implicit). Also, width and precision are replaced with their argument names when they exists. Since the issues were so closely related, this fix for issue #99265 also fixes issue #99266. Fixes #99265 Fixes #99266
2022-07-20	Add diagnostic width span when '0$' is used as width.	miam-miam100	-1/+19

2022-05-03	Make rustc_parse_format compile on stable	bjorn3	-103/+113
	This allows it to be used by lightweight formatting systems and may allow it to be used by rust-analyzer.
2022-03-30	Spellchecking compiler comments	Yuri Astrakhan	-1/+1
	This PR cleans up the rest of the spelling mistakes in the compiler comments. This PR does not change any literal or code spelling issues.
2022-02-16	Correctly mark the span of captured arguments in `format_args!()`	Chayim Refael Friedman	-8/+12
	It should only include the identifier, or misspelling suggestions will be wrong.
2021-07-08	Rework SESSION_GLOBALS API to prevent overwriting it	Guillaume Gomez	-2/+1

2021-05-24	remove cfg(bootstrap)	Pietro Albini	-1/+0

2021-03-28	Rollup merge of #83348 - osa1:issue83344, r=jackh726	Yuki Okushi	-4/+6
	format macro argument parsing fix When the character next to `{}` is "shifted" (when mapping a byte index in the format string to span) we should avoid shifting the span end index, so first map the index of `}` to span, then bump the span, instead of first mapping the next byte index to a span (which causes bumping the end span too much). Regression test added. Fixes #83344 --- r? ```@estebank```
2021-03-27	format macro argument parsing fix	Ömer Sinan Ağacan	-4/+6
	When the character next to `{}` is "shifted" (when mapping a byte index in the format string to span) we should avoid shifting the span end index, so first map the index of `}` to span, then bump the span, instead of first mapping the next byte index to a span (which causes bumping the end span too much). Regression test added. Fixes #83344
2021-03-27	Rollup merge of #83343 - osa1:issue83340, r=jackh726	Yuki Okushi	-14/+9
	Simplify and fix byte skipping in format! string parser Fixes '\\' handling in format strings. Fixes #83340
2021-03-21	Simplify and fix byte skipping in format! string parser	Ömer Sinan Ağacan	-14/+9
	Fixes '\\' handling in format strings. Fixes #83340
2021-03-19	stabilize or_patterns	mark	-1/+1

2021-02-06	parse_format: treat r" as a literal	David Hewitt	-1/+1

2021-01-17	rustc_parse_format: Fix character indices in find_skips	Ömer Sinan Ağacan	-1/+1
	Fixes #81006
2021-01-14	Use Option::map_or instead of `.map(..).unwrap_or(..)`	LingMan	-2/+2

2020-09-23	/nightly/nightly-rustc	Erik Hofmayer	-1/+1

2020-09-23	Updated html_root_url for compiler crates	Erik Hofmayer	-1/+1

2020-09-21	Rollup merge of #76888 - matthiaskrgr:clippy_single_match_2, r=Dylan-DPC	ecstatic-morse	-6/+3
	use if let instead of single match arm expressions use if let instead of single match arm expressions to compact code and reduce nesting (clippy::single_match)
2020-09-20	use if let instead of single match arm expressions to compact code and ↵	Matthias Krüger	-6/+3
	reduce nesting (clippy::single_match)
2020-09-17	Remove redundant #![feature(...)] 's from compiler/	est31	-2/+0

2020-08-30	mv compiler to compiler/	mark	-0/+1125