-
Notifications
You must be signed in to change notification settings - Fork 14k
Do we still need the NeverShortCircuit type?
#149157
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
base: main
Are you sure you want to change the base?
Conversation
This was added back before `ControlFlow` existed, when it was definitely better than `Result<T, !>` by avoiding the `From::from` calls. But now that we have `ControlFlow`, maybe we can avoid the extra type and impls? (Still keeps the helper methods for wrapping closures and such, of course.)
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Do we still need the `NeverShortCircuit` type?
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (af41280): comparison URL. Overall result: ❌ regressions - please read the text belowBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please do so in sufficient writing along with @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 3.8%, secondary -2.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.3%, secondary -1.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary 0.1%, secondary 0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 472.196s -> 473.178s (0.21%) |
This was added back before
ControlFlowexisted, when it was definitely better thanResult<T, !>by avoiding theFrom::fromcalls. But now that we haveControlFlow, maybe we can avoid the extra type and impls?(Still keeps the helper methods for wrapping closures and such, of course.)
r? ghost