https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.51.0 2021-02-13T15:43:07+00:00 2021-02-13T15:43:07+00:00 Ömer Sinan Ağacan omeragacan@gmail.com 2021-02-08T07:43:54+00:00 urn:sha1:853f7875a2258f11b62a6ea386d1ca289bb2a13d The panic happens when in recovery parsing a full `impl` (`parse_item_impl`) fails and we drop the `DiagnosticBuilder` for the recovery suggestion and return the `parse_item_impl` error. We now raise the original error "expected identifier found `impl`" when parsing the `impl` fails. Note that the regression test is slightly simplified version of the original repro in #81806, to make the error output smaller and more resilient to unrelated changes in parser error messages. Fixes #81806 2021-02-02T17:34:08+00:00 bors bors@rust-lang.org 2021-02-02T17:34:08+00:00 urn:sha1:3182375e064b8fa90437aee1465bccafd8187d89 Box the biggest ast::ItemKind variants This PR is a different approach on https://github.com/rust-lang/rust/pull/81400, aiming to save memory in humongous ASTs. The three affected item kind enums are: - `ast::ItemKind` (208 -> 112 bytes) - `ast::AssocItemKind` (176 -> 72 bytes) - `ast::ForeignItemKind` (176 -> 72 bytes) 2021-02-02T14:52:53+00:00 bors bors@rust-lang.org 2021-02-02T14:52:53+00:00 urn:sha1:b81f5811f96fe750ab28c15219d1b0dba6b1dc90 Bump rustfmt version 2021-02-02T14:09:52+00:00 Mark Rousskov mark.simulacrum@gmail.com 2021-01-09T17:00:45+00:00 urn:sha1:d5b760ba62b40dd770c09e704b8a3af64c1fd058 Also switches on formatting of the mir build module 2021-02-02T11:15:02+00:00 Jonas Schievink jonasschievink@gmail.com 2021-02-02T11:15:02+00:00 urn:sha1:255e0764c071d73a43a0c88181cb4cf667a74bff Improve handling of spans around macro result parse errors Fixes #81543 After we expand a macro, we try to parse the resulting tokens as a AST node. This commit makes several improvements to how we handle spans when an error occurs: * Only ovewrite the original `Span` if it's a dummy span. This preserves a more-specific span if one is available. * Use `self.prev_token` instead of `self.token` when emitting an error message after encountering EOF, since an EOF token always has a dummy span * Make `SourceMap::next_point` leave dummy spans unused. A dummy span does not have a logical 'next point', since it's a zero-length span. Re-using the span span preserves its 'dummy-ness' for other checks 2021-02-01T08:23:39+00:00 Dániel Buga bugadani@gmail.com 2021-01-29T07:31:08+00:00 urn:sha1:b87e1ecdf05d4fb2d14f13d760bb37098c58b06e 2021-01-31T20:24:34+00:00 Aaron Hill aa1ronham@gmail.com 2021-01-31T20:21:28+00:00 urn:sha1:6c14aad58e65c9c50faa45ed88369c5c72d6d0d7 Fixes #81543 After we expand a macro, we try to parse the resulting tokens as a AST node. This commit makes several improvements to how we handle spans when an error occurs: * Only ovewrite the original `Span` if it's a dummy span. This preserves a more-specific span if one is available. * Use `self.prev_token` instead of `self.token` when emitting an error message after encountering EOF, since an EOF token always has a dummy span * Make `SourceMap::next_point` leave dummy spans unused. A dummy span does not have a logical 'next point', since it's a zero-length span. Re-using the span span preserves its 'dummy-ness' for other checks 2021-01-31T00:47:34+00:00 Jonas Schievink jonasschievink@gmail.com 2021-01-31T00:47:34+00:00 urn:sha1:3e8ae5dcba4e5ad2f9a543df8da1ea679d84e4ce Clone entire `TokenCursor` when collecting tokens Reverts PR #80830 Fixes taiki-e/pin-project#312 We can have an arbitrary number of `None`-delimited group frames pushed on the stack due to proc-macro invocations, which can legally be exited. Attempting to account for this would add a lot of complexity for a tiny performance gain, so let's just use the original strategy. 2021-01-29T14:30:55+00:00 Ikko Ashimine eltociear@gmail.com 2021-01-29T14:30:55+00:00 urn:sha1:718398ccafaa45ed6a08ec550155150b9564eeed parentesized -> parenthesized 2021-01-28T14:47:59+00:00 Aaron Hill aa1ronham@gmail.com 2021-01-28T14:47:59+00:00 urn:sha1:5d739180cde7f7350b7a90e8a7542bd9c4cd6783 Reverts PR #80830 Fixes taiki-e/pin-project#312 We can have an arbitrary number of `None`-delimited group frames pushed on the stack due to proc-macro invocations, which can legally be exited. Attempting to account for this would add a lot of complexity for a tiny performance gain, so let's just use the original strategy.