rust/compiler/rustc_parse/src/parser, branch 1.88.0 https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.88.0 2025-05-09T03:57:49+00:00 Remove `Ident::empty`. 2025-05-09T03:57:49+00:00 Nicholas Nethercote n.nethercote@gmail.com 2025-04-24T01:56:44+00:00 urn:sha1:0984db553ddd25c0d16ef68b91bd731825309ac5 All uses have been removed. And it's nonsensical: an identifier by definition has at least one char. The commits adds an is-non-empty assertion to `Ident::new` to enforce this, and converts some `Ident` constructions to use `Ident::new`. Adding the assertion requires making `Ident::new` and `Ident::with_dummy_span` non-const, which is no great loss. The commit amends a couple of places that do path splitting to ensure no empty identifiers are created. Use `parse_param_general` when parsing `(T, U)->R` in `parse_path_segment` 2025-05-07T14:56:14+00:00 xizheyin xizheyin@smail.nju.edu.cn 2025-05-06T07:45:04+00:00 urn:sha1:b922da3586ce01a4bf174db09624a1d0a424d5d9 Signed-off-by: xizheyin <xizheyin@smail.nju.edu.cn> Co-authored-by: Vadim Petrochenkov <vadim.petrochenkov@gmail.com> Rollup merge of #140494 - ehuss:document-restrictions, r=traviscross,SparrowLii 2025-04-30T20:36:44+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-04-30T20:36:44+00:00 urn:sha1:a477172cedb83e1b8295bb20f4bff6e79f9e7bb1 Parser: Document restrictions I had trouble easily understanding what these various flags do. This is my attempt to try to explain what these do. ast: Remove token visiting from AST visitor 2025-04-30T07:36:03+00:00 Vadim Petrochenkov vadim.petrochenkov@gmail.com 2025-04-29T06:59:17+00:00 urn:sha1:6668d13de27be6382f06cbdc253d9a48f62e4c34 It's no longer necessary after the removal of nonterminal tokens in #124141. Parser: Document restrictions 2025-04-30T01:05:45+00:00 Eric Huss eric@huss.org 2025-04-30T01:05:45+00:00 urn:sha1:2b92f9fb98e16e3ed85166e14936be0c3f11c945 I had trouble easily understanding what these various flags do. This is my attempt to try to explain what these do. Use `ThinVec` to shrink `LazyAttrTokenStreamInner`. 2025-04-29T21:12:09+00:00 Nicholas Nethercote n.nethercote@gmail.com 2025-04-29T02:05:38+00:00 urn:sha1:880e6f716d741b4ef827d48e66c45c7887f82aa2 Simplify `LazyAttrTokenStream`. 2025-04-29T21:10:56+00:00 Nicholas Nethercote n.nethercote@gmail.com 2025-04-29T01:57:27+00:00 urn:sha1:298c56f4ba604d3c7025a44fe7bfe1134d6b56d6 This commit does the following. - Changes it from `Lrc<Box<dyn ToAttrTokenStream>>` to `Lrc<LazyAttrTokenStreamInner>`. - Reworks `LazyAttrTokenStreamImpl` as `LazyAttrTokenStreamInner`, which is a two-variant enum. - Removes the `ToAttrTokenStream` trait and the two impls of it. The recursion limit must be increased in some crates otherwise rustdoc aborts. Move various token stream things from `rustc_parse` to `rustc_ast`. 2025-04-29T02:14:27+00:00 Nicholas Nethercote n.nethercote@gmail.com 2025-04-29T01:18:08+00:00 urn:sha1:28236ab703d21483dc818108f157fbb2da5a2802 Specifically: `TokenCursor`, `TokenTreeCursor`, `LazyAttrTokenStreamImpl`, `FlatToken`, `make_attr_token_stream`, `ParserRange`, `NodeRange`. `ParserReplacement`, and `NodeReplacement`. These are all related to token streams, rather than actual parsing. This will facilitate the simplifications in the next commit. resolved conflict 2025-04-25T12:02:59+00:00 Kivooeo Kivooeo123@gmail.com 2025-04-25T10:55:44+00:00 urn:sha1:f072d3074170f1e70a6f6a1b309fa43f62c25a3c Rollup merge of #140228 - fmease:revert-overzealous-colon-recovery, r=jieyouxu 2025-04-24T09:40:47+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-04-24T09:40:47+00:00 urn:sha1:f45d2bd8ee55a8970093d9c3cbf7e456c926e8f6 Revert overzealous parse recovery for single colons in paths Basically manually reverts #136808, cc ``@chenyukang`` ``@estebank.`` Reopens #129273. Fixes [after beta backport] #140227.