-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Proposal: wait/fetch on Task #25928
Labels
domain:parallelism
Parallel or distributed computation
Comments
Working on a PR now |
iamed2
added a commit
to invenia/julia
that referenced
this issue
Feb 8, 2018
Triage accepts. |
iamed2
added a commit
to invenia/julia
that referenced
this issue
Feb 8, 2018
iamed2
added a commit
to invenia/julia
that referenced
this issue
Feb 9, 2018
Keno
pushed a commit
that referenced
this issue
Jun 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now
wait
has the same meaning for almost everything: wait for something to be available or for something to happen. WithTask
, it means the above plus get a result. For AbstractRemoteRef, this is whatfetch
does.I propose moving that functionality of
Task
tofetch
. Here's what it would look like in 0.7:and in 1.0:
How does this sound?
If this is not accepted I would still like to define
fetch(t::Task) = wait(t)
, as it has a clear meaning and allowsTask
s andFuture
s to be used interchangeably in some cases.The text was updated successfully, but these errors were encountered: