rust/tests/ui/parser/issues, branch lcnr/rustc-dev-guide

Added checks for attribute in type case

2025-08-05T02:10:31+00:00

Rollup merge of #138554 - xizheyin:issue-138401, r=chenyukang

2025-07-18T17:14:42+00:00

Distinguish delim kind to decide whether to emit unexpected closing delimiter Fixes #138401

Deduplicate `unmatched_delims` in `rustc_parse` to reduce confusion

2025-07-18T12:34:58+00:00

Signed-off-by: xizheyin

Rollup merge of #143921 - oli-obk:const-index, r=fee1-dead

2025-07-16T15:06:41+00:00

Constify `Index` traits tracking issue: rust-lang/rust#143775 the `SliceIndex` trait cannot be implemented by users as it is sealed. While it would be useful for the `get` method on slices, it seems weird to have a feature gate for that that isn't also gating index syntax at the same time, so I put them under the same feature gate. r? ```````@fee1-dead```````

constify `Index` trait and its slice impls

2025-07-15T08:27:15+00:00

Recover and suggest use `;` to construct array type

2025-07-15T04:00:46+00:00

Signed-off-by: xizheyin

Add ui test unnessary-error-issue-138401.rs

2025-07-07T07:27:01+00:00

Signed-off-by: xizheyin

Rewrite `macro_rules!` parser to not use the MBE engine itself

2025-06-26T22:20:42+00:00

The `macro_rules!` parser was written to match the series of rules using the macros-by-example (MBE) engine and a hand-written equivalent of the left-hand side of a MBE macro. This was complex to read, difficult to extend, and produced confusing error messages. Because it was using the MBE engine, any parse failure would be reported as if some macro was being applied to the `macro_rules!` invocation itself; for instance, errors would talk about "macro invocation", "macro arguments", and "macro call", when they were actually about the macro *definition*. And in practice, the `macro_rules!` parser only used the MBE engine to extract the left-hand side and right-hand side of each rule as a token tree, and then parsed the rest using a separate parser. Rewrite it to parse the series of rules using a simple loop, instead. This makes it more extensible in the future, and improves error messages. For instance, omitting a semicolon between rules will result in "expected `;`" and "unexpected token", rather than the confusing "no rules expected this token in macro call". This work was greatly aided by pair programming with Vincenzo Palazzo and Eric Holk.

Rollup merge of #142485 - mu001999-contrib:dead-code/adt-pattern, r=petrochenkov

2025-06-21T03:25:55+00:00

Marks ADT live if it appears in pattern Marks ADT live if it appears in pattern, it implies the construction of the ADT. 1. Then we can detect unused private ADTs impl `Default`, without special logics for `Default` and other std traits. 2. We can also remove `rustc_trivial_field_reads` on `Default`, and the logic in `should_ignore_item` (introduced by rust-lang/rust#126302). Fixes rust-lang/rust#120770 Extracted from rust-lang/rust#128637. r? `@petrochenkov`

Marks ADT live if it appears in pattern

2025-06-14T05:44:43+00:00