-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
delay_span_bug
when codegen cannot select obligation
#69614
Conversation
Fix rust-lang#69602, introduced in rust-lang#60126 by letting the compiler continue past type checking after encountering errors.
r? @davidtwco (rust_highfive has picked a reviewer for you, use r? to override) |
@bors r+ |
📌 Commit 7b6f5ed has been approved by |
`delay_span_bug` when codegen cannot select obligation Fix rust-lang#69602, introduced in rust-lang#60126 by letting the compiler continue past type checking after encountering errors.
Rollup of 10 pull requests Successful merges: - #69520 (Make error message clearer about creating new module) - #69589 (ast: `Mac`/`Macro` -> `MacCall`) - #69614 (`delay_span_bug` when codegen cannot select obligation) - #69641 (Update books) - #69674 (Rename DefKind::Method and TraitItemKind::Method ) - #69697 (Add explanation for E0380) - #69698 (Use associated constants of integer types) - #69705 (Toolstate: remove redundant beta-week check.) - #69711 (Update macros.rs: fix documentation typo.) - #69713 (more clippy cleanups) Failed merges: r? @ghost
`delay_span_bug` when codegen cannot select obligation Fix rust-lang#69602, introduced in rust-lang#60126 by letting the compiler continue past type checking after encountering errors.
@bors treeclosed=1000 msys2/MSYS2-packages#1884 |
@estebank Wouldn't it be simpler to just not run any codegen if there are errors? |
☀️ Test successful - checks-azure |
@eddyb that's fair, but from my cursory look we do have errors that were being elided before. The fewer iterations people need to fix their code, the better. That being said, we could stop after lifetime checking instead. |
@estebank Codegen should be separate from the rest of the compilation, in I agree on continuing after typeck, and we can continue after all the checks, as long as we don't let codegen start (which is strictly a waste of time). |
Fix #69602, introduced in #60126 by letting the compiler continue past
type checking after encountering errors.