-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
multiple Return terminators are possible #72563
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
I'd say that there are no restrictions at all on this terminator, instead of tying it to generators. For example, there were discussions about adding a pass that propagates terminators backwards, I believe, which would also duplicate Is there a reason to only have a single |
There was some discussion about this here #72022 (comment) |
Okay, I adjusted the comment accordingly. |
@bors r+ |
📌 Commit 8ef9392 has been approved by |
@bors rollup |
Rollup of 9 pull requests Successful merges: - rust-lang#72299 (more `LocalDefId`s) - rust-lang#72368 (Resolve overflow behavior for RangeFrom) - rust-lang#72441 (Fix ICE with explicit late-bound lifetimes) - rust-lang#72499 (Override Box::<[T]>::clone_from) - rust-lang#72521 (Properly handle InlineAsmOperand::SymFn when collecting monomorphized items) - rust-lang#72540 (mir: adjust conditional in recursion limit check) - rust-lang#72563 (multiple Return terminators are possible) - rust-lang#72585 (Only capture tokens for items with outer attributes) - rust-lang#72607 (Eagerly lower asm sub-expressions to HIR even if there is an error) Failed merges: r? @ghost
@ecstatic-morse mentioned in #72515 that multiple
Return
terminators are possible. Update the docs accordingly.Cc @rust-lang/wg-mir-opt