Skip to content
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.

Sign up for GitHub

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

Jump to bottom

No way to force par_iter to run in parallel and not fall back to sequential execution #13

Closed
kaksmet opened this issue Jan 4, 2016 · 1 comment
Closed

No way to force par_iter to run in parallel and not fall back to sequential execution #13

kaksmet opened this issue Jan 4, 2016 · 1 comment

Comments

@kaksmet
Copy link

kaksmet commented Jan 4, 2016

Currently there is no way to force par_iter to run in parallel and not fall back to sequential execution (except setting weight to an arbitrarily high value).

I think a simple method that guarantees the par_iter will run in parallel would suffice.
@nikomatsakis
Copy link
Member

Currently there is no way to force par_iter to run in parallel and not fall back to sequential execution (except setting weight to an arbitrarily high value).

What is wrong with that? I imagined something like weight(f64::INFINITY).

nikomatsakis added a commit that referenced this issue Jan 23, 2016
@nikomatsakis
Add a weight_max method as a nice shorthand. Fixes #13.
422397a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nikomatsakis @kaksmet