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

Remove std::par #5626

Closed
brson opened this issue Mar 29, 2013 · 4 comments · Fixed by #9380
Closed

Remove std::par #5626

brson opened this issue Mar 29, 2013 · 4 comments · Fixed by #9380
Labels
A-concurrency Area: Concurrency E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@brson
Copy link
Contributor

brson commented Mar 29, 2013

Just a few parallel algorithms. This is unused and probably not efficient enough for real use. If we're going to do this it will need to be rethought from scratch.
@thestinger
Copy link
Contributor

Is it possible to add an API that would spawn a task assigned to an exclusive OS thread?

@brson
Copy link
Contributor Author

brson commented Mar 30, 2013

@thestinger There is already a way to do that by creating a task with the SingleThreaded scheduler mode. The mechanism may change with the new scheduler, but it's an important use case so there will continue to be a way to dedicate an entire thread to a single task.

@nickdesaulniers
Copy link

assign=me

@emberian
Copy link
Member

@nickdesaulniers did this land? if not do you want to rebase your patch?

@thestinger thestinger mentioned this issue Sep 21, 2013
Merged
bors added a commit that referenced this issue Sep 21, 2013
@bors
auto merge of #9380 : thestinger/rust/par, r=alexcrichton
44dc3fb 
This was a dead end experiment, and not a sensible way of implementing
generic data parallelism. This also removes the `graph500-bfs.rs`
benchmark because it relies on `extra::par`.

Closes #5626
flip1995 pushed a commit to flip1995/rust that referenced this issue Jul 14, 2020
@bors
Auto merge of rust-lang#5694 - wangtheo:issue-5626, r=matthiaskrgr
583d644 
rust-lang#5626: lint iterator.map(|x| x)

changelog: adds a new lint for iterator.map(|x| x) (see rust-lang/rust-clippy#5626)

The code also lints for result.map(|x| x) and option.map(|x| x). Also, I'm not sure if I'm checking for type adjustments correctly and I can't think of an example where .map(|x| x) would apply type adjustments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-concurrency Area: Concurrency E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

drop extra::par
4 participants
@brson @emberian @thestinger @nickdesaulniers