-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Replace @async
mentions in manual with Threads.@spawn
#55315
Conversation
Re-add Base.@async to parallel.md
Tangentially related issue: |
Would it make sense to merge the multi-threading and asynchronous programming pages at this point? Tasks seem to be the main way to do either at this point, and single-threaded asynchronous programming is now basically a special case of the parallel + concurrent model (if I understand correctly). Alternatively, it could make sense to refactor them into a "how to" page focused on Tasks, and a lower-level details page focused on Atomics, Threadpools, etc. I could take a stab at it if there's interest. |
Thank you for your contribution! This PR looks great. @giordano, documenting |
I believe these make more sense as async than spawn, otherwise more orchestration is needed in the example. Were changed to spawn in JuliaLang#55315
I believe these make more sense as async than spawn, otherwise more orchestration is needed in the example. Were changed to spawn in JuliaLang#55315
According to #50356,
@async
is no longer recommended and new code should useThreads.@spawn
. However, the manual still mentions@async
in several places. This PR updates the user-visible mentions of@async
toThreads.@spawn
. I made sure tomake docs
locally afterwards and check that the references were updated.Note: I'm not experienced with open source, so please let me know how I could clean up this PR or do things better. I tried to follow the contributing guidelines as closely as possible but it's likely I missed something.