ziglang/zig
259
6.0k
Fork
You've already forked zig
771

Io.Dispatch: introduce grand central dispatch io impl #31198

Merged
andrewrk merged 2 commits from dispatch into master 2026年02月13日 23:19:35 +01:00

Still plenty of unimplemented features, but the compiler already runs.

Still plenty of unimplemented features, but the compiler already runs.
crash_report: finish reverting panic changes better
All checks were successful
ci / x86_64-netbsd-release (pull_request) Successful in 30m31s
ci / x86_64-freebsd-release (pull_request) Successful in 31m10s
ci / x86_64-netbsd-debug (pull_request) Successful in 40m7s
ci / x86_64-freebsd-debug (pull_request) Successful in 42m18s
ci / aarch64-macos-release (pull_request) Successful in 42m6s
ci / x86_64-windows-debug (pull_request) Successful in 44m11s
ci / x86_64-windows-release (pull_request) Successful in 48m17s
ci / aarch64-macos-debug (pull_request) Successful in 54m33s
ci / x86_64-openbsd-release (pull_request) Successful in 56m5s
ci / x86_64-openbsd-debug (pull_request) Successful in 57m53s
ci / aarch64-linux-release (pull_request) Successful in 1h28m18s
ci / x86_64-linux-debug (pull_request) Successful in 1h12m39s
ci / aarch64-linux-debug (pull_request) Successful in 2h21m4s
ci / powerpc64le-linux-release (pull_request) Successful in 1h33m43s
ci / s390x-linux-release (pull_request) Successful in 1h22m46s
ci / x86_64-linux-debug-llvm (pull_request) Successful in 2h53m39s
ci / riscv64-linux-debug (pull_request) Has been skipped
ci / riscv64-linux-release (pull_request) Has been skipped
ci / powerpc64le-linux-debug (pull_request) Successful in 3h49m35s
ci / x86_64-linux-release (pull_request) Successful in 3h51m34s
ci / s390x-linux-debug (pull_request) Successful in 3h36m54s
0eb1e0c30a 
I missed that the types were `pub`.
andrewrk left a comment
Copy link

Huh, interesting, so it still uses fibers created independently from libdispatch? One thing I didn't figure out from reading the code is how does thread spawning work?

Huh, interesting, so it still uses fibers created independently from libdispatch? One thing I didn't figure out from reading the code is how does thread spawning work?
@ -0,0 +2770,4 @@
constrc=c.getdirentries(dr.dir.handle,dents_buffer.ptr,dents_buffer.len,&header.seek);
switch(c.errno(rc)){
.SUCCESS=>break@intCast(rc),
.INTR=>{},
Owner
Copy link

no cancel checks?

no cancel checks?
Author
Owner
Copy link

Currently only mutex (not Io.Mutex) and futex have intentionally designed cancellation, but select and group may accidentally work from being copied from a similar enough io impl.

Currently only mutex (not `Io.Mutex`) and futex have intentionally designed cancellation, but select and group may accidentally work from being copied from a similar enough io impl.

Don't forget to create followup issues to track unimplemented features, to invite contributors to help out!

Don't forget to create followup issues to track unimplemented features, to invite contributors to help out!
andrewrk scheduled this pull request to auto merge when all checks succeed 2026年02月13日 22:52:57 +01:00
Author
Owner
Copy link

@andrewrk wrote in #31198 (comment):

Huh, interesting, so it still uses fibers created independently from libdispatch?

Otherwise libdispatch would create one thread per async, and you would just end up with a threaded impl with no thread limit and no interesting evented properties.

@andrewrk wrote in https://codeberg.org/ziglang/zig/pulls/31198#issuecomment-10566320: > Huh, interesting, so it still uses fibers created independently from libdispatch? Otherwise libdispatch would create one thread per async, and you would just end up with a threaded impl with no thread limit and no interesting evented properties.

What's the benefit of libdispatch, compared to kqueue?

What's the benefit of libdispatch, compared to kqueue?
Author
Owner
Copy link

Recursive directory watching on macos already introduces a dependency on libdispatch, at which point your choices are to use an io impl based on libdispatch, or to have file watching behave like a blocking, synchronous syscall with respect to kqueue. If we knew the lower level abi of the fs event log service (I don't) and if it were stable (unlikely) we could connect it to a kqueue impl ourself.

Recursive directory watching on macos already introduces a dependency on libdispatch, at which point your choices are to use an io impl based on libdispatch, or to have file watching behave like a blocking, synchronous syscall with respect to kqueue. If we knew the lower level abi of the fs event log service (I don't) and if it were stable (unlikely) we could connect it to a kqueue impl ourself.

Also kqueue IIRC is implemented on top of GCD so it's a similiar situation to kernel32 vs ntdll

Also kqueue IIRC is implemented on top of GCD so it's a similiar situation to kernel32 vs ntdll
First-time contributor
Copy link

DispatchSource is built on top of kqueue, and the most important feature of libdispatch, in my opinion, is its ability to dynamically spawn and retire pthreads through the lower-level pthread_workqueue API, which is integrated throughout Darwin system APIs such as XPC and Network.framework.

DispatchSource is built on top of kqueue, and the most important feature of libdispatch, in my opinion, is its ability to dynamically spawn and retire pthreads through the lower-level pthread_workqueue API, which is integrated throughout Darwin system APIs such as XPC and Network.framework.
Author
Owner
Copy link

Ok I take it back, the protocol is dead simple and there is little room for misinterpretation.

Ok I take it back, the protocol is dead simple and there is little room for misinterpretation.

Also kqueue IIRC is implemented on top of GCD so it's a similiar situation to kernel32 vs ntdll

I believe it's the other way around, GCD is implemented on top of kqueue.

> Also kqueue IIRC is implemented on top of GCD so it's a similiar situation to kernel32 vs ntdll I believe it's the other way around, GCD is implemented on top of kqueue.
Sign in to join this conversation.
No reviewers
Labels
Clear labels
abi/f32
abi/ilp32
abi/sf
accepted
This proposal is planned.
arch/21k
arch/6502
arch/aarch64
arch/alpha
arch/amdgcn
arch/arc
arch/arc32
arch/arc64
arch/arm
arch/avr
arch/bfin
arch/bpf
arch/colossus
arch/cris
arch/csky
arch/dlx
arch/epiphany
arch/fr30
arch/frv
arch/hexagon
arch/hppa
arch/hppa64
arch/ia64
arch/kalimba
arch/kvx
arch/lanai
arch/lm32
arch/loongarch32
arch/loongarch64
arch/m32r
arch/m68k
arch/m88k
arch/mcore
arch/microblaze
arch/mips
arch/mips64
arch/mmix
arch/moxie
arch/mrisc32
arch/msp430
arch/nds32
arch/ns32k
arch/nvptx
arch/or1k
arch/powerpc
arch/powerpc64
arch/propeller
arch/riscv32
arch/riscv64
arch/rl78
arch/rx
arch/s390x
arch/sh
arch/sparc
arch/sparc64
arch/spirv
arch/spu
arch/tricore
arch/v850
arch/vax
arch/vc4
arch/ve
arch/wasm
arch/x86
arch/x86_64
arch/xcore
arch/xtensa
autodoc
The web application for interactive documentation and generation of its assets.
backend/c
The C backend outputs C source code.
backend/llvm
The LLVM backend outputs an LLVM bitcode module.
backend/self-hosted
The self-hosted backends produce machine code directly.
binutils
Zig's included binary utilities: zig ar, zig dlltool, zig lib, zig ranlib, zig objcopy, and zig rc.
breaking
Implementing this issue could cause existing code to no longer compile or have different behavior.
build system
The Zig build system - zig build, std.Build, the build runner, and package management.
debug info
An issue related to debug information (e.g. DWARF) produced by the Zig compiler.
docs
An issue with documentation, e.g. the language reference or standard library doc comments.
error message
This issue points out an error message that is unhelpful and should be improved.
frontend
Tokenization, parsing, AstGen, ZonGen, Sema, Legalize, and Liveness.
fuzzing
An issue related to Zig's integrated fuzz testing.
incremental
Reuse of internal compiler state for faster compilation.
lib/c
This issue relates to Zig's libc implementation and/or vendored libcs.
lib/compiler-rt
This issue relates to Zig's compiler-rt library.
lib/cxx
This issue relates to Zig's vendored libc++ and/or libc++abi.
lib/std
This issue relates to Zig's standard library.
lib/tsan
This issue relates to Zig's vendored libtsan.
lib/ubsan-rt
This issue relates to Zig's ubsan-rt library.
lib/unwind
This issue relates to Zig's vendored libunwind.
linking
Zig's integrated object file and incremental linker.
miscompilation
The compiler reports success but produces semantically incorrect code.
os/android
os/contiki
os/dragonfly
os/driverkit
os/emscripten
os/freebsd
os/fuchsia
os/haiku
os/hermit
os/hurd
os/illumos
os/ios
os/linux
os/maccatalyst
os/macos
os/managarm
os/netbsd
os/ohos
os/openbsd
os/plan9
os/redox
os/rtems
os/serenity
os/tvos
os/uefi
os/visionos
os/wasi
os/watchos
os/windows
proposal
This issue suggests language modifications. If it also has the "accepted" label then it is planned.
release notes
This issue or pull request should be mentioned in the release notes.
testing
This issue is related to testing the compiler, standard library, or other parts of Zig.
zig cc
Zig as a drop-in C-family compiler.
zig fmt
The Zig source code formatter.
zig reduce
The Zig source code reduction tool.
bounty
https://ziglang.org/news/announcing-donor-bounties
bug
Observed behavior contradicts documented or intended behavior.
contributor-friendly
This issue is limited in scope and/or knowledge of project internals.
downstream
An issue with a third-party project that uses this project.
enhancement
Solving this issue will likely involve adding new logic or components to the codebase.
infra
An issue related to project infrastructure, e.g. continuous integration.
optimization
A task to improve performance and/or resource usage.
question
No questions on the issue tracker; use a community space instead.
regression
Something that used to work in a previous version stopped working
upstream
An issue with a third-party project that this project uses.
use case
Describes a real use case that is difficult or impossible, but does not propose a solution.
No labels
abi/f32
abi/ilp32
abi/sf
accepted
arch/21k
arch/6502
arch/aarch64
arch/alpha
arch/amdgcn
arch/arc
arch/arc32
arch/arc64
arch/arm
arch/avr
arch/bfin
arch/bpf
arch/colossus
arch/cris
arch/csky
arch/dlx
arch/epiphany
arch/fr30
arch/frv
arch/hexagon
arch/hppa
arch/hppa64
arch/ia64
arch/kalimba
arch/kvx
arch/lanai
arch/lm32
arch/loongarch32
arch/loongarch64
arch/m32r
arch/m68k
arch/m88k
arch/mcore
arch/microblaze
arch/mips
arch/mips64
arch/mmix
arch/moxie
arch/mrisc32
arch/msp430
arch/nds32
arch/ns32k
arch/nvptx
arch/or1k
arch/powerpc
arch/powerpc64
arch/propeller
arch/riscv32
arch/riscv64
arch/rl78
arch/rx
arch/s390x
arch/sh
arch/sparc
arch/sparc64
arch/spirv
arch/spu
arch/tricore
arch/v850
arch/vax
arch/vc4
arch/ve
arch/wasm
arch/x86
arch/x86_64
arch/xcore
arch/xtensa
autodoc
backend/c
backend/llvm
backend/self-hosted
binutils
breaking
build system
debug info
docs
error message
frontend
fuzzing
incremental
lib/c
lib/compiler-rt
lib/cxx
lib/std
lib/tsan
lib/ubsan-rt
lib/unwind
linking
miscompilation
os/android
os/contiki
os/dragonfly
os/driverkit
os/emscripten
os/freebsd
os/fuchsia
os/haiku
os/hermit
os/hurd
os/illumos
os/ios
os/linux
os/maccatalyst
os/macos
os/managarm
os/netbsd
os/ohos
os/openbsd
os/plan9
os/redox
os/rtems
os/serenity
os/tvos
os/uefi
os/visionos
os/wasi
os/watchos
os/windows
proposal
release notes
testing
zig cc
zig fmt
zig reduce
bounty
bug
contributor-friendly
downstream
enhancement
infra
optimization
question
regression
upstream
use case
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ziglang/zig!31198
Reference in a new issue
ziglang/zig
No description provided.
Delete branch "dispatch"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?