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

Age	Commit message (Collapse)	Author	Lines
2018-09-22	Rollup merge of #54409 - estebank:remove-in, r=pnkfelix	Pietro Albini	-9/+25
	Detect `for _ in in bar {}` typo Fix #36611, #52964, without modifying the parsing of emplacement `in` to avoid further problems like #50832.
2018-09-22	Rollup merge of #54261 - varkor:dyn-keyword-2018, r=petrochenkov	Pietro Albini	-2/+3
	Make `dyn` a keyword in the 2018 edition Proposed in https://github.com/rust-lang/rust/issues/44662#issuecomment-421596088.
2018-09-20	Detect `for _ in in bar {}` typo	Esteban Küber	-9/+25

2018-09-21	parser: Tweak function parameter parsing to avoid rollback on succesfull path	Vadim Petrochenkov	-36/+26

2018-09-17	Whitespace fix again.	Vitaly _Vi Shukela	-5/+5

2018-09-17	Fill in suggestions Applicability according to @estebank	Vitaly _Vi Shukela	-5/+6
	Also fix some formatting along the way.
2018-09-16	Treat `dyn` as a keyword in the 2018 edition	varkor	-2/+3

2018-09-16	Remove usages of span_suggestion without Applicability	Vitaly _Vi Shukela	-1/+5
	Use Applicability::Unspecified for all of them instead.
2018-09-15	issue 54109: use short suggestions	Vitaly _Vi Shukela	-4/+4

2018-09-13	Use span_suggestion_with_applicability for "and/or" hinter	Vitaly _Vi Shukela	-4/+24
	Advised by @estebank.
2018-09-13	Suggest && and \|\| instead of 'and' and 'or'	Vitaly _Vi Shukela	-0/+13
	Closes #54109.
2018-09-10	pretty=expanded should expand mod declarations	Tinco Andringa	-3/+3

2018-09-10	Track whether module declarations are inline (fixes #12590)	Tinco Andringa	-5/+12

2018-09-09	Auto merge of #53902 - dtolnay:group, r=petrochenkov	bors	-10/+12
	proc_macro::Group::span_open and span_close Before this addition, every delimited group like `(`...`)` `[`...`]` `{`...`}` has only a single Span that covers the full source location from opening delimiter to closing delimiter. This makes it impossible for a procedural macro to trigger an error pointing to just the opening or closing delimiter. The Rust compiler does not seem to have the same limitation: ```rust mod m { type T = } ``` ```console error: expected type, found `}` --> src/main.rs:3:1 \| 3 \| } \| ^ ``` On that same input, a procedural macro would be forced to trigger the error on the last token inside the block, on the entire block, or on the next token after the block, none of which is really what you want for an error like above. This commit adds `group.span_open()` and `group.span_close()` which access the Span associated with just the opening delimiter and just the closing delimiter of the group. Relevant to Syn as we implement real error messages for when parsing fails in a procedural macro: https://github.com/dtolnay/syn/issues/476. ```diff impl Group { fn span(&self) -> Span; + fn span_open(&self) -> Span; + fn span_close(&self) -> Span; } ``` Fixes #48187 r? @alexcrichton
2018-09-08	Track distinct spans for open and close delimiter	David Tolnay	-10/+12

2018-09-04	Move #[test_case] to a syntax extension	John Renner	-1/+0

2018-09-02	Replace check() + bump() with eat()	Seiichi Uchida	-20/+10

2018-09-01	Auto merge of #53815 - F001:if-let-guard, r=petrochenkov	bors	-2/+2
	refactor match guard This is the first step to implement RFC 2294: if-let-guard. Tracking issue: https://github.com/rust-lang/rust/issues/51114 The second step should be introducing another variant `IfLet` in the Guard enum. I separated them into 2 PRs for the convenience of reviewers. r? @petrochenkov
2018-08-30	Rollup merge of #53655 - jcpst:with_applicability, r=estebank	Pietro Albini	-2/+12
	set applicability Update a few more calls as described in #50723 r? @estebank
2018-08-30	introduce Guard enum	F001	-2/+2

2018-08-25	call span_suggestion with applicability	Joseph Post	-2/+12

2018-08-24	fix compile error	Mark Mansi	-1/+1

2018-08-24	Remove anon trait params from 2018 and beyond	Mark Mansi	-1/+7

2018-08-24	Rollup merge of #53563 - matthiaskrgr:String, r=varkor	kennytm	-7/+7
	use String::new() instead of String::from(""), "".to_string(), "".to_owned() or "".into()
2018-08-23	Auto merge of #52602 - scottmcm:tryblock-expr, r=nikomatsakis	bors	-10/+30
	Implement try block expressions I noticed that `try` wasn't a keyword yet in Rust 2018, so... ~~Fixes https://github.com/rust-lang/rust/issues/52604~~ That was fixed by PR https://github.com/rust-lang/rust/pull/53135 cc https://github.com/rust-lang/rust/issues/31436 https://github.com/rust-lang/rust/issues/50412
2018-08-23	use String::new() instead of String::from(""), "".to_string(), "".to_owned() ↵	Matthias Krüger	-7/+7
	or "".into()
2018-08-22	Rollup merge of #53585 - dtolnay:comment, r=Mark-Simulacrum	Guillaume Gomez	-2/+0
	Remove super old comment on function that parses items This comment was added more than 5 years ago in ab03c1e4221. As far as anyone reading this comment today needs to know, the function has never parsed items from inside an extern crate.
2018-08-22	Rollup merge of #53544 - estebank:issue-53534, r=varkor	Guillaume Gomez	-7/+8
	Point at the trait argument when using unboxed closure Fix #53534. r? @varkor
2018-08-21	Remove super old comment on function that parses items	David Tolnay	-2/+0
	This comment was added more than 5 years ago in ab03c1e4221. As far as anyone reading this comment today needs to know, the function has never parsed items from inside an extern crate.
2018-08-21	Rollup merge of #53496 - matthiaskrgr:codespell_08_2018, r=varkor	kennytm	-5/+5
	Fix typos found by codespell.
2018-08-20	Point at the trait argument when using unboxed closure	Esteban Küber	-7/+8

2018-08-19	Switch out another use of `do catch`	Scott McMurray	-1/+9

2018-08-19	Suggest `try` if someone uses `do catch`	Scott McMurray	-0/+12

2018-08-19	Parse try blocks with the try keyword instead of do catch placeholder	Scott McMurray	-11/+11

2018-08-19	Rename `Catch` variants to `TryBlock`	Scott McMurray	-1/+1
	(Not `Try` since `QuestionMark` is using that.)
2018-08-19	mv codemap source_map	Donato Sciarra	-3/+3

2018-08-19	mv codemap() source_map()	Donato Sciarra	-19/+19

2018-08-19	mv (mod) codemap source_map	Donato Sciarra	-10/+10

2018-08-19	mv CodeMap SourceMap	Donato Sciarra	-2/+2

2018-08-19	Fix typos found by codespell.	Matthias Krüger	-5/+5

2018-08-17	Rollup merge of #53360 - PramodBisht:issue/51602, r=estebank	kennytm	-1/+7
	Addressed #51602 Fixed #51602 r? @estebank here I have addressed the case where `in` was not expected right after `if` block. Speaking of `type ascription` I am not sure if this the best approach which I have implemented. Plus I think one more test case can be added to test `type-ascription` case, though I don't have any at this point of time. I will ping you again if all existing testcases pass.
2018-08-15	syntax: Enforce attribute grammar in the parser	Vadim Petrochenkov	-1/+1

2018-08-14	Adddressed #51602	Pramod Bisht	-1/+7

2018-08-13	Move SmallVec and ThinVec out of libsyntax	ljedrz	-1/+1

2018-08-11	Clean up and add extra tests	varkor	-12/+3

2018-08-11	Add E0642 to parser error	varkor	-3/+6

2018-08-11	Emit an error during parsing	varkor	-42/+62

2018-08-11	Improve diagnostics	varkor	-1/+1

2018-08-11	Fix handling of trait methods with bodies and improve efficiency	varkor	-19/+30

2018-08-11	Emit error for pattern arguments in trait methods	varkor	-20/+33
	The error and check for this already existed, but the parser didn't try to parse trait method arguments as patterns, so the error was never emitted. This surfaces the error, so we get better errors than simple parse errors.