rust/compiler/rustc_parse/src/parser/ty.rs, branch automation/bors/try-mergehttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=automation/bors/try-merge2025-09-16T18:38:08+00:00Detect top-level `...` in argument type2025-09-16T18:38:08+00:00Esteban Küberesteban@osdyne.com2025-09-16T18:38:08+00:00urn:sha1:e9270e3cba3da56d4d83ed74f648e53b041cb263
When writing something like the expression `|_: ...| {}`, we now detect the `...` during parsing explicitly instead of relying on the detection in `parse_ty_common` so that we don't talk about "nested `...` are not supported".
```
error: unexpected `...`
--> $DIR/no-closure.rs:6:35
|
LL | const F: extern "C" fn(...) = |_: ...| {};
| ^^^
|
= note: only `extern "C"` and `extern "C-unwind"` functions may have a C variable argument list
```
Less greedily parse `[const]` bounds2025-09-10T21:24:31+00:00León Orell Valerian Liehrme@fmease.dev2025-09-10T19:41:00+00:00urn:sha1:f5dad62d4cdf139fb1c6cf2fa24ac525167501ccRestore the test intention of several MBE trait bound modifier tests2025-09-10T21:24:31+00:00León Orell Valerian Liehrme@fmease.dev2025-09-10T19:40:24+00:00urn:sha1:1558e65c9eec9ee0309e1920266e0a4325b63784Rollup merge of #144897 - fee1-dead-contrib:raw_lifetimes_printing, r=fmease2025-08-23T02:00:47+00:00Jacob Prattjacob@jhpratt.dev2025-08-23T02:00:47+00:00urn:sha1:2dbd411d229ee382b1cf2ec3af84cd581d56d521
print raw lifetime idents with r#
This replaces rust-lang/rust#143185 and fixes rust-lang/rust#143150
cc ``@fmease``
Recover param: Ty = EXPR2025-08-22T19:45:28+00:00Michael Gouletmichael@errs.io2025-02-21T17:39:49+00:00urn:sha1:6caa586f572429fd08a5df7283a97666d898d043address review comments2025-08-22T05:16:44+00:00Deadbeefent3rm4n@gmail.com2025-08-22T05:06:49+00:00urn:sha1:4970127c33a2cfd7b7035daedba7cac512a2e201Rollup merge of #145474 - fmease:paren-use-bounds-fix, r=fee1-dead2025-08-19T11:45:33+00:00许杰友 Jieyou Xu (Joe)39484203+jieyouxu@users.noreply.github.com2025-08-19T11:45:33+00:00urn:sha1:b638266f232ff260d7693ef7bb0a0d3051351369
Properly recover from parenthesized use-bounds (precise capturing lists) plus small cleanups
Fixes https://github.com/rust-lang/rust/issues/145470.
First commit fixes the issue, second one performs some desperately needed cleanups.
The fix shouldn't be a breaking change because IINM the parser always ensures that all brackets are balanced (via a buffer of brackets). Meaning even though we used to accept `(use<>` as a valid precise capturing list, it was guaranteed that we would fail in the end.
Clean up parsers related to generic bounds2025-08-16T14:15:58+00:00León Orell Valerian Liehrme@fmease.dev2025-08-15T21:01:32+00:00urn:sha1:f8f7c27d4f723913a6929e591c612865a7b62f70Properly recover from parenthesized use-bounds (precise capturing)2025-08-15T23:21:35+00:00León Orell Valerian Liehrme@fmease.dev2025-08-15T20:14:37+00:00urn:sha1:eb3e0d4c8a5599db0a4624662e5ab59380be8cd2Add FnContext in parser for diagnostic2025-08-14T13:31:47+00:00xizheyinxizheyin@smail.nju.edu.cn2025-08-14T13:30:52+00:00urn:sha1:3ce555f6313e78d3eed80fd22e22ef49f5bd3611
Signed-off-by: xizheyin <xizheyin@smail.nju.edu.cn>