Konrad `ktoso` Malawski
1e2047c6c3
CI: Temporarily disable taskExecutor test with Task.immediate
...
rdar://155596073 Task executors execution may not always hop as expected
I'm investigating a fix here as we speak, but disabling the specific piece of the test while we work on it.
2025-07-14 19:35:46 +09:00
Konrad 'ktoso' Malawski
664be9bd1e
[Concurrency] Add missing Task.immediateDetached, which drops task locals
2025-07-10 14:57:44 +09:00
Konrad 'ktoso' Malawski
358c3e9dcf
[Concurrency] a few missing overloads for immediate tasks
2025-07-10 12:40:41 +09:00
Pavel Yaskevich
8c4f7e97c8
Revert "[Concurrency] Remove deprecated Task.startSynchronously API"
2025-07-08 13:54:23 -07:00
Pavel Yaskevich
e108524d98
[Concurrency] Remove deprecated Task.startSynchronously API
...
This is the original spelling which was not accepted. We kept
it for a bit to give adopters time to switch but it's time to
remove it now.
2025-07-07 00:31:19 -07:00
Konrad 'ktoso' Malawski
3aa28b4de9
[Concurrency] Correct memory effect attributes of task_create
...
Without this, llvm would sometimes wrongly assume there's no indirect
accesses and the optimizations can lead to a runtime crash, by
optimizing away initializing options properly.
Resolves rdar://152548190
2025-06-11 22:03:52 +09:00
Pavel Yaskevich
c3c1b4fca0
[stdlib] Adopt @_inheritActorContext(always) on Task.immediate
...
This change aligns implementation with the current SE-0472 proposal.
2025-05-16 14:27:46 -07:00
Pavel Yaskevich
001eab867d
[stdlib] SE-0472: Rename Task and*TaskGroup APIs to match the proposal
...
`Task.startSynchronously` -> `Task.immediate`
`*TaskGroup.startTaskSynchronously{UnlessCancelled}` -> `*TaskGroup.addImmediateTask{UnlessCancelled}`
2025-05-09 23:59:30 -07:00
