https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.67.1 2022-12-06T12:27:41+00:00 2022-12-06T12:27:41+00:00 Matthias Krüger matthias.krueger@famsik.de 2022-12-06T12:27:41+00:00 urn:sha1:48172ff64b17b3e927e97af0b1f19a8754cade83 propagate the error from parsing enum variant to the parser and emit out While parsing enum variant, the error message always disappear Because the error message that emit out is from main error of parser The information of enum variant disappears while parsing enum variant with error We only check the syntax of expecting token, i.e, in case https://github.com/rust-lang/rust/issues/103869 It will error it without telling the message that this error is from pasring enum variant. Propagate the sub-error from parsing enum variant to the main error of parser by chaining it with map_err Check the sub-error before emitting the main error of parser and attach it. Fix https://github.com/rust-lang/rust/issues/103869 2022-12-05T19:43:44+00:00 Matthias Krüger matthias.krueger@famsik.de 2022-12-05T19:43:44+00:00 urn:sha1:66a4cb5368873fd793c53884e30dd543c4cad04c suggest parenthesis around ExprWithBlock BinOp ExprWithBlock fix https://github.com/rust-lang/rust/issues/105179 fix https://github.com/rust-lang/rust/issues/102171 2022-12-04T15:25:32+00:00 Matthias Krüger matthias.krueger@famsik.de 2022-12-04T15:25:32+00:00 urn:sha1:b1816833bd9f0d38c1866e883c261aafe1767485 Fix ICE on invalid variable declarations in macro calls This fixes ICE that happens with invalid variable declarations in macro calls like: ```rust macro_rules! m { ($s:stmt) => {} } m! { var x } m! { auto x } m! { mut x } ``` Found this is because of not collecting tokens on recovery, so I changed to force collect them. Fixes https://github.com/rust-lang/rust/issues/103529. 2022-12-03T22:54:06+00:00 Lukas Markeffsky @ 2022-12-03T22:54:06+00:00 urn:sha1:c808d0b289c1f8e0f26885bf44cb2ba1873ba10e 2022-12-03T19:02:39+00:00 Lukas Markeffsky @ 2022-12-03T19:02:39+00:00 urn:sha1:35c00a9731809292959e98b1e7da3c6e2673f3cc 2022-12-03T16:37:41+00:00 Matthias Krüger matthias.krueger@famsik.de 2022-12-03T16:37:41+00:00 urn:sha1:c89bff29e562540c14497aa8cc8490e6a2cdeb73 Keep track of the start of the argument block of a closure This removes a call to `tcx.sess.source_map()` from [compiler/rustc_trait_selection/src/traits/error_reporting/mod.rs](https://github.com/rust-lang/rust/compare/master...SarthakSingh31:issue-97417-1?expand=1#diff-8406bbc0d0b43d84c91b1933305df896ecdba0d1f9269e6744f13d87a2ab268a) as required by #97417. VsCode automatically applied `rustfmt` to the files I edited under `src/tools`. I can undo that if its a problem. r? `@cjgillot` 2022-12-03T14:41:42+00:00 Yutaro Ohno yutaro.ono.418@gmail.com 2022-12-03T14:37:23+00:00 urn:sha1:e4812583c70db2259b952829a7412dea96c5afdd Previously, the `recover_local_after_let` function was called from the body of the `recover_stmt_local` function. Unifying these two functions make it more simple and more readable. 2022-12-03T14:24:49+00:00 Yutaro Ohno yutaro.ono.418@gmail.com 2022-12-03T14:24:49+00:00 urn:sha1:690addc6ecc575f6b9df5e2fc09bd119e51e6194 Fix ICE on parsing an invalid variable declaration as a statement like: ``` macro_rules! m { ($s:stmt) => {} } m! { var x } ``` 2022-12-02T06:48:52+00:00 Yiming Lei yiming.lei@futurewei.com 2022-11-30T20:01:00+00:00 urn:sha1:0e19fb92e1eb7f91aa5570b2ac782c9a42a6e329 Because the error message that emit out is from main error of parser The information of enum variant disappears while parsing enum variant with error We only check the syntax of expecting token, i.e, in case #103869 It will error it without telling the message that this error is from pasring enum variant. Propagate the sub-error from parsing enum variant to the main error of parser by chaining it with map_err Check the sub-error before emitting the main error of parser and attach it. Fix #103869 2022-12-01T15:51:20+00:00 Vadim Petrochenkov vadim.petrochenkov@gmail.com 2022-12-01T15:51:20+00:00 urn:sha1:b32a4edb2078ca61ebcd9bad993905873f4a990a Lower them into a single item with multiple resolutions instead. This also allows to remove additional `NodId`s and `DefId`s related to those additional items.