diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-01-17 20:21:20 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-17 20:21:20 +0100 |
| commit | 22f19130df52f63821e1321c5949c421f781a21f (patch) | |
| tree | 630e06bf736be33127da469dc69fe3092cde9245 /compiler/rustc_pattern_analysis/src/errors.rs | |
| parent | c9779afc9c095638b44a4db740d816c7e7dcc4d6 (diff) | |
| parent | 22833c177e23c1c80e7ad1cbea33d758dcd94c28 (diff) | |
| download | rust-22f19130df52f63821e1321c5949c421f781a21f.tar.gz rust-22f19130df52f63821e1321c5949c421f781a21f.zip | |
Rollup merge of #119975 - lukas-code:inferring-return-types-and-opaque-types-do-mix-sometimes, r=compiler-errors
Don't ICE if TAIT-defining fn contains a closure with `_` in return type The `delay_span_bug` got added in https://github.com/rust-lang/rust/pull/119803/commits/0e82aaeb6799041991c54fb9ff37b5c20a5c6146 to reduce the amount of errors emitted for functions that have `_` in their return type, because inference doesn't apply to function items. But this logic shouldn't apply to closures, because their return types *can* be inferred. Fixes https://github.com/rust-lang/rust/issues/119916.
Diffstat (limited to 'compiler/rustc_pattern_analysis/src/errors.rs')
0 files changed, 0 insertions, 0 deletions
