-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
feat: optional rayon #13552
Open
lightsing
wants to merge
5
commits into
paradigmxyz:main
Choose a base branch
from
scroll-tech:feat/opt-rayon
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
feat: optional rayon #13552
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lightsing
requested review from
rkrasiuk,
Rjected,
shekhirin,
joshieDo,
mattsse,
klkvr and
gakonst
as code owners
December 25, 2024 02:09
lightsing
force-pushed
the
feat/opt-rayon
branch
from
December 25, 2024 02:24
afa7b8f
to
1a318a0
Compare
CodSpeed Performance ReportMerging #13552 will degrade performances by 10.66%Comparing Summary
Benchmarks breakdown
|
mattsse
reviewed
Dec 25, 2024
Comment on lines
+96
to
+101
/// Helper trait that requires rayon since `rayon` feature is enabled. | ||
#[cfg(feature = "rayon")] | ||
pub trait MaybeIntoParallelIterator: | ||
rayon::iter::IntoParallelIterator<Item = <Self as MaybeIntoParallelIterator>::Item> | ||
+ IntoIterator<Item = <Self as MaybeIntoParallelIterator>::Item> | ||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not really a fan of this,
I think I'd rather two recovery fns instead
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
related issue: #13443
todo: when alloy-core is bumped to a release contains alloy-rs/core#827, propagate feature to
alloy-primitives/rayon