diff options
| author | bors <bors@rust-lang.org> | 2024-07-11 11:51:33 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-07-11 11:51:33 +0000 |
| commit | c92a8e4d4d7e8da53aa05309ef8d4fac2c9af52f (patch) | |
| tree | 7366a2d07a1f1136b94e7706056dc0b0d7fa260e /tests/codegen/wasm_exceptions.rs | |
| parent | fdf7ea6b5b1cac83c0f29e681202cf18bf25b01c (diff) | |
| parent | dce98c52ff3e431d9b1358298fe8da9db545a3e2 (diff) | |
| download | rust-c92a8e4d4d7e8da53aa05309ef8d4fac2c9af52f.tar.gz rust-c92a8e4d4d7e8da53aa05309ef8d4fac2c9af52f.zip | |
Auto merge of #127311 - oli-obk:do_not_count_errors, r=compiler-errors
Avoid follow-up errors and ICEs after missing lifetime errors on data structures Tuple struct constructors are functions, so when we call them typeck will use the signature tuple struct constructor function to provide type hints. Since typeck mostly ignores and erases lifetimes, we end up never seeing the error lifetime in writeback, thus not tainting the typeck result. Now, we eagerly taint typeck results by tainting from `resolve_vars_if_possible`, which is called all over the place. I did not carry over all the `crashes` test suite tests, as they are really all the same cause (missing or unknown lifetime names in tuple struct definitions or generic arg lists). fixes #124262 fixes #124083 fixes #125155 fixes #125888 fixes #125992 fixes #126666 fixes #126648 fixes #127268 fixes #127266 fixes #127304
Diffstat (limited to 'tests/codegen/wasm_exceptions.rs')
0 files changed, 0 insertions, 0 deletions