ability to "bundle" more errors before the first suspend point in an async function #1197
Labels
proposal
This issue suggests modifications. If it also has the "accepted" label then it is planned.
Milestone
Comments
andrewrk
added
the
proposal
andrewrk
added a commit
that referenced
this issue
Jul 7, 2018
* add std.atomic.QueueMpsc.isEmpty * make std.debug.global_allocator thread-safe * std.event.Loop: now you have to choose between - initSingleThreaded - initMultiThreaded * std.event.Loop multiplexes coroutines onto kernel threads * Remove std.event.Loop.stop. Instead the event loop run() function returns once there are no pending coroutines. * fix crash in ir.cpp for calling methods under some conditions * small progress self-hosted compiler, analyzing top level declarations * Introduce std.event.Lock for synchronizing coroutines * introduce std.event.Locked(T) for data that only 1 coroutine should modify at once. * make the self hosted compiler use multi threaded event loop * make std.heap.DirectAllocator thread-safe See #174 TODO: * call sched_getaffinity instead of hard coding thread pool size 4 * support for Windows and MacOS * #1194 * #1197
|
I created #1260 for the first bullet point. I'll let this issue become the second bullet point. |
andrewrk
changed the title
|
Obsoleted with the merge of #3033. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'll expand on this later but I need an issue to link to.
awaitin the same stack frame that youasync, there does not need to be a coroutine allocation.asyncbefore the first suspend point in a coroutine frame, this can be made to not fail, because the allocation could have been bundled up with the callee's coroutine frameThe text was updated successfully, but these errors were encountered: