diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-01-18 06:59:20 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-01-18 06:59:20 +0100 |
| commit | d26e07b91a48047c0acd1e5527f49e57902eb6e7 (patch) | |
| tree | 921f74cb479669d10caf95b2bd7a1957dc8b60f0 /tests/rustdoc-js-std/parser-errors.js | |
| parent | 7e6f42e688b4e1713533f369b54df19ea7aca104 (diff) | |
| parent | aadd58ef7a78c3eabc75c73db6b166debdd7f1d2 (diff) | |
| download | rust-d26e07b91a48047c0acd1e5527f49e57902eb6e7.tar.gz | |
Rollup merge of #106747 - yanchen4791:issue-105507-fix, r=estebank
Add 'static lifetime suggestion when GAT implied 'static requirement from HRTB
Fix for issue #105507
The problem:
When generic associated types (GATs) are from higher-ranked trait bounds (HRTB), they are implied 'static requirement (see
[Implied 'static requirement from higher-ranked trait bounds](https://blog.rust-lang.org/2022/10/28/gats-stabilization.html#implied-static-requirement-from-higher-ranked-trait-bounds) for more details). If the user did not explicitly specify the `'static` lifetime when using the GAT, the current error message will only point out the type `does not live long enough` where the type is used, but not where the GAT is specified and how to fix the problem.
The solution:
Add notes at the span where the problematic GATs are specified and suggestions of how to fix the problem by adding `'static` lifetime at the right spans.
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions