Option->Result->Option used in ?-on-Option isn't a no-op #49437
Labels
A-codegen
Area: Code generation
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
I-slow
Issue: Problems and improvements with respect to performance of generated code.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
(Very similar to the rebuild-the-same-Result in #38349, but a bit more complex.)
Ideally
foo
would just^= 1
the discriminant, andbar
would be a nop, but todayhttps://play.rust-lang.org/?gist=dc3fab4d8a20e31552769a9a03504c4c&version=nightly&mode=release
The text was updated successfully, but these errors were encountered: