bors 6f3030f316 Auto merge of #17586 - ShoyuVanilla:tuple-arg-macro-rest, r=Veykril ... Allow macro expansions into `RestPat` in tuple args work as ellipsis like plain `RestPat` Fixes #17292 Currently, Rust Analyzer lowers `ast::Pat::RestPat` into `Pat::Missing` in general cases on the following lines; ffbc5ad993/crates/hir-def/src/body/lower.rs (L1359-L1367) And in some proper positions such as `TupleStruct(..)`, it is specially handed on the following lines; ffbc5ad993/crates/hir-def/src/body/lower.rs (L1429-L1437) This behavior is reasonable because rustc does similar things in 62c068feea/compiler/rustc_ast_lowering/src/pat.rs (L108-L111) and 62c068feea/compiler/rustc_ast_lowering/src/pat.rs (L123-L142) But this sometimes works differently because Rust Analyzer expands macros while ast lowering; ffbc5ad993/crates/hir-def/src/body/lower.rs (L1386-L1398) ffbc5ad993/crates/hir-def/src/body/lower.rs (L941-L963) but rustc uses expanded ast in the corresponding tuple-handling process, so it does not have macro patterns there. 62c068feea/compiler/rustc_ast_lowering/src/pat.rs (L114) So, if a macro expansion in a tuple arg results in `..`, rustc permits it like plain `..` pattern, but Rust Analyzer rejects it. This is the root cause of #17292 and this PR allows macros expanded into `..` in a tuple arg position work as ellipsis like that.		2024-07-22 09:08:12 +00:00
..
src	Auto merge of #17586 - ShoyuVanilla:tuple-arg-macro-rest, r=Veykril	2024-07-22 09:08:12 +00:00
Cargo.toml	internal: Enforce utf8 paths	2024-03-19 15:39:00 +01:00