Repository navigation
[runtime] FIXME cluster needs fix + test #48
Description
File
src/runtime/socket/SocketAddress.zig:495 (zig-legacy permalink)
Pattern
FIXME × 2 candidate(s) in area/runtime.
Matched snippet(s):
src/runtime/ffi/ffi.zig:507: // FIXME: why are we duping here? can we at least use a stack
src/runtime/socket/SocketAddress.zig:495: // FIXME: c-headers-for-zig casts AF_* and PF_* to `c_int` when it should be `comptime_int`Upstream relevance
not found— searchedoven-sh/bunissues forruntime FIXME; no verified applicable match (re-check withgh search issues --repo oven-sh/bun "<keywords>"before closing as fork-specific).
Repro
rg -n "TODO|FIXME|unimplemented|throwTODO|todo_stuff|@compileError" src/runtime/socket/SocketAddress.zig | head
vendor/zig/zig build check 2>&1 | head -30Expected: path is implemented or explicitly gated with a tracked issue. Actual: hard-stop marker (@compileError / @panic(TODO) / throwTODO / stub) on a reachable path.
Suggested next step
Implement the stub / replace the hard stop with a propagated error + test in the mapped test/js/... suite per AGENTS.md (or gate the platform explicitly and keep this issue as the tracker).
Harvest metadata
commit: 8ceabb0958pattern: FIXMEcandidate-ids: src/runtime/ffi/ffi.zig:507, src/runtime/socket/SocketAddress.zig:495generated-by: bun-zig-triage (harvest.sh + dedupe.py)
Activity