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

Age	Commit message (Collapse)	Author	Lines
2019-06-10	Harden non-const items to not accept underscore names.	Mazdak Farrokhzad	-11/+122

2019-06-09	Allow attributes in formal function parameters	Caio	-32/+32

2019-06-09	Update tests since ? macro op is supported on 2015.	Mazdak Farrokhzad	-2/+2

2019-06-08	Prohibit bare CRs in raw byte strings	Igor Matuszewski	-4/+13

2019-06-08	Validate and transcribe raw strings via unescape module	Igor Matuszewski	-4/+4

2019-06-03	Auto merge of #61331 - estebank:fn-arg-parse-recovery, r=varkor	bors	-1/+23
	Recover gracefully from argument with missing type or param name
2019-06-01	Rollup merge of #61403 - estebank:test-cleanup, r=petrochenkov	Mazdak Farrokhzad	-167/+104
	Remove unnecessary `-Z continue-parse-after-error` from tests r? @petrochenkov
2019-05-31	fix tidy	Esteban Küber	-166/+103

2019-05-30	Remove unecessary `-Z continue-parse-after-error` from tests	Esteban Küber	-31/+31

2019-05-30	Recover gracefully from argument with missing type or param name	Esteban Küber	-1/+23

2019-05-30	Explicitly suggest 'type_ascription' feature	Janusz Marcinkiewicz	-1/+1

2019-05-28	Update test/ui/parser for bare_trait_object warnings	memoryruins	-12/+43

2019-05-25	review comments: move back some methods and clean up wording	Esteban Küber	-4/+4

2019-05-25	Tweak `self` arg not as first argument of a method diagnostic	Esteban Küber	-0/+13
	Mention that `self` is only valid on "associated functions" ``` error: unexpected `self` argument in function --> $DIR/self-in-function-arg.rs:1:15 \| LL \| fn foo(x:i32, self: i32) -> i32 { self } \| ^^^^ not valid as function argument \| = note: `self` is only valid as the first argument of an associated function ``` When it is a method, mention it must be first ``` error: unexpected `self` argument in function --> $DIR/trait-fn.rs:4:20 \| LL \| fn c(foo: u32, self) {} \| ^^^^ must be the first associated function argument ```
2019-05-24	review comments	Esteban Küber	-0/+0

2019-05-24	Tweak macro parse errors when reaching EOF during macro call parse	Esteban Küber	-0/+12
	- Add detail on origin of current parser when reaching EOF and stop saying "found <eof>" and point at the end of macro calls - Handle empty `cfg_attr` attribute - Reword empty `derive` attribute error
2019-05-24	Auto merge of #60803 - varkor:remove-in-place-syntax, r=petrochenkov	bors	-3/+0
	Remove `ObsoleteInPlace` The in place syntax has been deprecated for over a year. As it is, this is accumulated cruft: the error messages are unlikely to be helpful any more and it conflicts with some useful syntax (e.g. const generics in some instances). It may be that removing `Token::LArrow` is backwards-incompatible. We should do a crater run to check. cc @eddyb
2019-05-24	Update tests	varkor	-3/+0

2019-05-24	Rollup merge of #61056 - euclio:custom-discriminant-error, r=estebank	Mazdak Farrokhzad	-10/+18
	tweak discriminant on non-nullary enum diagnostic Adds notes pointing at the non-nullary variants, and uses "custom discriminant" language to be consistent with the Reference. Fixes #61039. r? @estebank
2019-05-23	tweak discriminant on non-nullary enum diagnostic	Andy Russell	-10/+18
	Adds notes pointing at the non-nullary variants, and uses "custom discriminant" language to be consistent with the Reference.
2019-05-23	syntax: Some code cleanup	Vadim Petrochenkov	-15/+17

2019-05-23	syntax: More consistent wording for some literal parsing errors	Vadim Petrochenkov	-16/+16

2019-05-23	syntax: Return named errors from literal parsing functions	Vadim Petrochenkov	-3/+3

2019-05-20	Reinstated shallow disallowing of maybe bounds in trait objects.	Alexander Regueiro	-2/+16

2019-05-20	Update tests.	Alexander Regueiro	-17/+3

2019-05-11	Move literal parsing code into a separate file	Vadim Petrochenkov	-4/+4
	Remove some dead code
2019-05-09	Rollup merge of #60188 - estebank:recover-block, r=varkor	Mazdak Farrokhzad	-8/+186
	Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar. Fix #54186, cc #54482, fix #59975, fix #47287.
2019-05-02	fix typo	Esteban Küber	-12/+12

2019-05-02	introduce unescape module	Aleksey Kladov	-77/+120
	Currently, we deal with escape sequences twice: once when we lex a string, and a second time when we unescape literals. This PR aims to remove this duplication, by introducing a new `unescape` mode as a single source of truth for character escaping rules
2019-04-30	Reword ambigous parse error to fit with the current error	Esteban Küber	-8/+8

2019-04-29	Add test case for #47287	Esteban Küber	-1/+25

2019-04-29	Identify when a stmt could have been parsed as an expr	Esteban Küber	-3/+157
	There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-25	Rollup merge of #60160 - xldenis:fix-overlapping-zero-width-annotation, ↵	Mazdak Farrokhzad	-3/+2
	r=estebank Fix #58270, fix off-by-one error in error diagnostics. This fixes #58270 by checking if two diagnostics overlap completely when we're calculating the line offset for each message.
2019-04-23	Remove unnecessary tidy ignore directives	varkor	-8/+5

2019-04-22	Fix #58270, fix off-by-one error in error diagnostics.	Xavier Denis	-3/+2

2019-04-19	Some cleanup to `maybe_parse_struct_expr`	Vadim Petrochenkov	-0/+1

2019-04-19	Emit specific error for struct literal in conditions	Esteban Küber	-156/+92

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

2019-04-11	review comments	Esteban Küber	-2/+2

2019-04-10	Recover from missing semicolon based on the found token	Esteban Küber	-0/+52
	When encountering one of a few keywords when a semicolon was expected, suggest the semicolon and recover: ``` error: expected one of `.`, `;`, `?`, or an operator, found `let` --> $DIR/recover-missing-semi.rs:4:5 \| LL \| let _: usize = () \| - help: missing semicolon here LL \| LL \| let _ = 3; \| ^^^ error[E0308]: mismatched types --> $DIR/recover-missing-semi.rs:2:20 \| LL \| let _: usize = () \| ^^ expected usize, found () \| = note: expected type `usize` found type `()` ```
2019-04-01	Rollup merge of #59041 - saleemjaffer:trait_doc_comment_better_error_msg, ↵	Mazdak Farrokhzad	-0/+17
	r=pnkfelix fixes rust-lang#56766 fixes #56766
2019-03-31	Rollup merge of #59572 - davidtwco:issue-59508, r=varkor	Mazdak Farrokhzad	-5/+5
	Include bounds in generic re-ordering diagnostic Fixes #59508. r? @estebank cc @varkor
2019-03-31	Only mention const generics if enabled.	David Wood	-5/+5
	This commit updates the generic parameter re-ordering diagnostic to only mention const generics if the feature is enabled.
2019-03-30	Rollup merge of #59453 - estebank:recover-tuple-parse, r=petrochenkov	Mazdak Farrokhzad	-4/+124
	Recover from parse error in tuple syntax
2019-03-29	revert change to test file as per review request	Esteban Küber	-2/+1

2019-03-29	Rollup merge of #59467 - hgallagher1993:local_branch, r=estebank	Mazdak Farrokhzad	-2/+4
	Better diagnostic for binary operation on BoxedValues Fixes #59458
2019-03-28	fix text after rebase	Esteban Küber	-0/+8

2019-03-28	Rollup merge of #59408 - euclio:compiletest-normalization, r=oli-obk	Mazdak Farrokhzad	-71/+71
	compiletest: make path normalization smarter Fixes #59109.
2019-03-28	Recover from parse error in tuple syntax	Esteban Küber	-5/+118

2019-03-28	Rollup merge of #59198 - estebank:recovered-pattern, r=zackmdavis	Mazdak Farrokhzad	-18/+2
	Do not complain about unmentioned fields in recovered patterns When the parser has to recover from malformed code in a pattern, do not complain about missing fields. Fix #59145.