diff options
| author | Urgau <3616612+Urgau@users.noreply.github.com> | 2024-10-16 12:03:43 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-16 12:03:43 +0200 |
| commit | 329e5704604ca677562a8f8e69b18c008f8cca15 (patch) | |
| tree | 07b686976f04678584dd2562b9a9f724ce7f444b /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | 66dc09f3dacce171389b0861a320aaeb6f95f659 (diff) | |
| parent | 68885216b63f6e75e50b4c0f3c7250ca4ac7afda (diff) | |
| download | rust-329e5704604ca677562a8f8e69b18c008f8cca15.tar.gz rust-329e5704604ca677562a8f8e69b18c008f8cca15.zip | |
Rollup merge of #131754 - compiler-errors:bivariance-bivariance, r=estebank
Don't report bivariance error when nesting a struct with field errors into another struct
We currently have logic to avoid reporting lifetime bivariance ("lifetime parameter ... is never used") errors when a struct has field resolution errors. However, this doesn't apply transitively. This PR implements a simple visitor to do so.
This was reported [here](https://twitter.com/fasterthanlime/status/1846257921086165033) since a `derive(Deserialize, Serialize)` ends up generating helper structs which have bivariant lifetimes due to containing the offending struct (that's being derived on).
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions