Uh oh!
There was an error while loading. Please reload this page.
delay_span_bug when codegen cannot select obligation - #69614
Conversation
Fixrust-lang#69602, introduced in rust-lang#60126 by letting the compiler continue past type checking after encountering errors.
rust-highfive
commented
Mar 1, 2020
r? @davidtwco (rust_highfive has picked a reviewer for you, use r? to override) |
davidtwco
commented
Mar 2, 2020
@bors r+ |
bors
commented
Mar 2, 2020
📌 Commit 7b6f5ed has been approved by |
`delay_span_bug` when codegen cannot select obligation Fixrust-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 Fixrust-lang#69602, introduced in rust-lang#60126 by letting the compiler continue past type checking after encountering errors.
bors
commented
Mar 6, 2020
emilyalbini
commented
Mar 6, 2020
@bors treeclosed=1000 msys2/MSYS2-packages#1884 |
@estebank Wouldn't it be simpler to just not run any codegen if there are errors? |
bors
commented
Mar 6, 2020
☀️ Test successful - checks-azure |
estebank
commented
Mar 6, 2020
@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.