Update threadingconstructs.jl #39309
Merged
Conversation
This file contains hidden or 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
I try to make clearer that the task **is scheduled** to run on an available thread. This makes an important difference since between the creation of the task and its allocation to a thread may be a time delay. see: [discussion on Discourse](https://discourse.julialang.org/t/looking-for-code-to-solve-surely-common-embarrassing-parallelism-multithreading-use-case/53527/9)
JeffBezanson
added
docs
base/threadingconstructs.jl
Outdated
| Create a [`Task`](@ref) and [`schedule`](@ref) it to run on any available thread. | ||
| The task is allocated to a thread after it becomes available. | ||
| To wait for the task to finish, call [`wait`](@ref) on the result of this macro, or |
Member
There was a problem hiding this comment.
Please remove the trailing whitespace here.
trailing whitespace removed
fredrikekre
reviewed
Jan 19, 2021
Co-authored-by: Fredrik Ekre <ekrefredrik@gmail.com>
ElOceanografo
pushed a commit
to ElOceanografo/julia
that referenced
this pull request
May 4, 2021
I try to make clearer that the task **is scheduled** to run on an available thread. This makes an important difference since between the creation of the task and its allocation to a thread may be a time delay. see: [discussion on Discourse](https://discourse.julialang.org/t/looking-for-code-to-solve-surely-common-embarrassing-parallelism-multithreading-use-case/53527/9)
antoine-levitt
pushed a commit
to antoine-levitt/julia
that referenced
this pull request
May 9, 2021
I try to make clearer that the task **is scheduled** to run on an available thread. This makes an important difference since between the creation of the task and its allocation to a thread may be a time delay. see: [discussion on Discourse](https://discourse.julialang.org/t/looking-for-code-to-solve-surely-common-embarrassing-parallelism-multithreading-use-case/53527/9)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I try to make clearer that the task is scheduled to run on an available thread. This makes an important difference since between the creation of the task and its allocation to a thread may be a time delay.
see: discussion on Discourse