-
Notifications
You must be signed in to change notification settings - Fork 14k
Implement the alternative try block desugaring
#148725
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
Conversation
|
rustbot has assigned @petrochenkov. Use |
This comment has been minimized.
This comment has been minimized.
74cc941 to
88085e3
Compare
This comment has been minimized.
This comment has been minimized.
88085e3 to
cfbecaf
Compare
cfbecaf to
86c3ba7
Compare
|
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
8b90701 to
cc7f844
Compare
tests/mir-opt/pre-codegen/option_bubble_debug.option_traits.PreCodegen.after.panic-abort.mir
Outdated
Show resolved
Hide resolved
This comment has been minimized.
This comment has been minimized.
|
This comment has been minimized.
This comment has been minimized.
ae3a70e to
1e2fe0d
Compare
This comment has been minimized.
This comment has been minimized.
1e2fe0d to
e5803fc
Compare
|
@bors r+ |
Rollup of 4 pull requests Successful merges: - #148638 (Fix ICE for repr simd on non struct) - #148725 (Implement the alternative `try` block desugaring) - #148777 (Lock shards while emitting depth limit error.) - #148933 (Add note for option llvm.download-ci-llvm) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of #148725 - scottmcm:experiment-new-try-block-v3, r=petrochenkov Implement the alternative `try` block desugaring As discussed in rust-lang/rfcs#3721 (comment), update the `try` in nightly to match the RFC as a way to experiment. This addresses the following unresolved issue from #31436 > Address issues with type inference (`try { expr? }?` currently requires an explicit type annotation somewhere).
As discussed in rust-lang/rfcs#3721 (comment), update the
tryin nightly to match the RFC as a way to experiment.This addresses the following unresolved issue from #31436