Repository navigation
[test_runner] FIXME cluster needs fix + test #53
Description
File
src/test_runner/expect/toBeEmpty.zig:39 (zig-legacy permalink)
Pattern
FIXME × 1 candidate(s) in area/test_runner.
Matched snippet(s):
src/test_runner/expect/toBeEmpty.zig:39: // FIXME: can we do this?Upstream relevance
not found— searchedoven-sh/bunissues fortest_runner 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/test_runner/expect/toBeEmpty.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/test_runner/expect/toBeEmpty.zig:39generated-by: bun-zig-triage (harvest.sh + dedupe.py)
Activity