diff options
| author | 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com> | 2025-08-19 19:45:33 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-19 19:45:33 +0800 |
| commit | b638266f232ff260d7693ef7bb0a0d3051351369 (patch) | |
| tree | 2e3c5898ff757fb7f7286481b8cd1912322a2878 /tests/rustdoc-js-std/parser-reference.js | |
| parent | 9a5c00a673e68c05fd520682dedecb81d9cbc89f (diff) | |
| parent | f8f7c27d4f723913a6929e591c612865a7b62f70 (diff) | |
| download | rust-b638266f232ff260d7693ef7bb0a0d3051351369.tar.gz rust-b638266f232ff260d7693ef7bb0a0d3051351369.zip | |
Rollup merge of #145474 - fmease:paren-use-bounds-fix, r=fee1-dead
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.
Diffstat (limited to 'tests/rustdoc-js-std/parser-reference.js')
0 files changed, 0 insertions, 0 deletions