You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tasks can now migrate among threads when they are re-scheduled. Previously, a Task would always run on whichever thread executed it first (#40715).
But the docs do not seem to be updated accordingly. They still say, that:
After a task starts running on a certain thread (e.g. via @Spawn), it will always be restarted on the same thread after blocking. In the future this limitation will be removed, and tasks will migrate between threads.
I guess the future is now?
The text was updated successfully, but these errors were encountered:
The NEWS file states that:
Tasks can now migrate among threads when they are re-scheduled. Previously, a Task would always run on whichever thread executed it first (#40715).
But the docs do not seem to be updated accordingly. They still say, that:
After a task starts running on a certain thread (e.g. via @Spawn), it will always be restarted on the same thread after blocking. In the future this limitation will be removed, and tasks will migrate between threads.
I guess the future is now?
The text was updated successfully, but these errors were encountered: