diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-11-12 08:07:19 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-11-12 08:07:19 +0100 |
| commit | 9a4a95435980db865eb104f0af4d7d6e0f958f66 (patch) | |
| tree | c4901b5b126d24030d80503fb5c9fb490fe2cf73 /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | ea61714d524c81400b979d32955dcac8c8241562 (diff) | |
| parent | d128c80c7aeb936bdb587734e599b1bdb7c1e442 (diff) | |
| download | rust-9a4a95435980db865eb104f0af4d7d6e0f958f66.tar.gz rust-9a4a95435980db865eb104f0af4d7d6e0f958f66.zip | |
Rollup merge of #132935 - compiler-errors:arg-math, r=nnethercote
Make sure to ignore elided lifetimes when pointing at args for fulfillment errors
See the comment I left in the code.
---
If we have something like:
```
fn foo<'a, T: 'a + BoundThatIsNotSatisfied>() {}
```
And the user turbofishes just the type args:
```
foo::<()>();
```
Then if we try pointing at `()` (i.e. the type argument for `T`), we don't actually consider the possibility that the lifetimes may have been left out of the turbofish. We try indexing incorrectly into the HIR args, and bail on the suggestion.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
