ziglang/zig

Fork 771

Code Issues 706 Pull requests 292 Activity Actions 25

Tracking Issue: Issues that need tests to be closed #31661

New issue

Open

opened 2026年03月25日 12:58:43 +01:00 by K4 · 9 comments

K4 commented

2026年03月25日 12:58:54 +01:00

Author

Contributor

Copy link

Also, these issues seem to be fixed and seem to not need tests:

(done) #576
(done) #747
probably #1487 see #1487 (comment)
#1534 by a newer LLVM version
#1790
#1882 see #1882 (comment)
#2209
#2349 see #2349 (comment)
#3125
#3609 now gives error instead of miscompilation
(done) #3821 by a newer LLVM version
#3884 see #3884 (comment)
#5191 part of #31131 which is resolved
#5244 see #5244 (comment)
#7354
#7357 has test in test/behavior/switch.zig named "switch on pointer type"
#7774
#8087 std.os.argv is removed by PR #30644
#8997 by a newer LLVM version, see #8997 (comment)
#9215 see #9215 (comment)
#9472 see #9472 (comment)
#9638
#10185 now arrays in packed struct gives compiler error
#10328 now gives error: variable of type 'test.KpcApi__struct_22508' must be const or comptime
#10389 see #10389 (comment), the duplicate is closed
#10412 see #10412 (comment), the duplicate is closed
#11367 I think this is fixed by PR #31403
probably #12266
#12344
#12473 (I tested only with the release build of the zig compiler)
#13123 not a problem with the current API
(done) #13129
#13509
#13578 now gives error: dependency loop with length 2
somewhat #13807
#13915 see #13915 (comment), Debian 13 "Trixie" has been realeased since
#14052 see #14052 (comment), if not duplicate it needs a test
#14088 see #14088 (comment)
#14089 see #14089 (comment), this is not a bug as labeled
#14211 see #14211 (comment)
#14318 usingnamespace has been removed
#14564 now gives error: asm cannot output to const 'val_low'
#14727 see #14727 (comment)
#14873 see #14873 (comment)
#14888 see #14888 (comment)
#14960 see #14960 (comment)
#15154
#15165 repro is to big for a test
probably #15254
(done) #15368
#15504
probably #15547
#15601 see #15601 (comment)
#15646 unless "this is the kind of thing that can be caught and warned about at build time" from #15646 (comment)
#15999
#16343
#16410 not a problem with the current API
probably #16432 based on my little amount of testing
#16437 now gives error: value in memory does not match slice sentinel
(done) #16479
#16523 should be closed or labeled as error message, not as bug
#16525 see #16525 (comment)
(done) #16758 by a newer LLVM version
#16775 should be closed or labeled as error message, not as bug; see #16775 (comment)
#17024 because there is Module.addOptions
#17073 now gives error: type '@EnumLiteral()' does not support field access
#17360 now gives error: field bit width does not match earlier field
#17401 now gives error: type 'test.MyStruct' depends on itself for alignment query here
probably #17515
(done) #17574 now gives error: packed structs cannot contain fields of type '*const fn () void'
#17626 see #17626 (comment)
#17650
(done) #17676 see #17676 (comment)
#17710 see #17710 (comment)
#17745 now gives General protection exception (no address available)
#17775
(done) #17856 now gives error: packed structs cannot contain fields of type '[*]const u8'
probably #17908
probably #18018
probably #18050
#18113 now gives error: unable to resolve comptime value
#18147
#18223 now gives error: unable to perform tail call: compiler backend 'stage2_x86_64' does not support tail calls on target architecture 'x86_64' with the selected CPU feature flags
#18263
#18273 now gives error: error set is discarded
(done) #18359
#18459 see #18459 (comment)
#18495
#18627 see #18627 (comment)
(done) #18747 see #18747 (comment)
probably #18820
probably #18830
#18842
#18854 now gives error: union field order does not match tag enum field order
#18884
#18928
#18953
#18995 now gives panic: integer does not fit in destination type
#19011
(done) #19037
#19045
#19098
#19105
#19165
#19209 see #19209 (comment)
#19211 now gives panic: invalid enum value (maybe it should say panic: invalid union value?)
probably #19369
#19386
#19423 can be closed or changed to be a doc issue, see #19423 (comment)
#19443
#19476 superseded by #30659
#19578 now gives error: non-scalar sentinel type 'example.Code'
probably #19685
probably #19870 (also PR #19871 should be closed)
#19935 was fixed in 0.15.1
#19979 fixed in PR #21755 (any further issue is covered by #1516, see #19979 (comment))
#20016
#20067 errdefer |err| has been removed in PR #32130
#20076
#20079
#20154 now gives error: parameter of type 'noreturn' not allowed and has already a test case
#20208
#20221 now gives more notes
#20320
#20332
#20347
#20369 errdefer |err| has been removed in PR #32130
probably #20406 @alexrp Can you confirm this?
possibly #20453 because now gives error: expected type '[5]@Vector(5, usize)', found '[5][5]usize'
probably #20458
#20461 now gives a note along with error:
Main.zig:1:1: note: declared here const Point2D = @import("Point.zig").Point;
#20501 (at least with doas instead of sudo)
#20505 due to commit c895aa7a35
#20524 I believe does not apply anymore
#20539 by PR #31403
#20562
#20566 now gives error: reached unreachable code
#20601 is fixed, but sometimes gives a error that I presume it's already known:

error: sub-compilation of compiler_rt failed
 note: failed to check cache: '/home/user/.zig-master/lib/compiler_rt.zig' file_hash FileNotFound

probably #20606
probably #20612
probably #20665
probably #20676
#20680
#20752 now gives error: expected type 'test.Range', found 'struct { usize, usize }'
#20793 now gives:

error: failed to spawn and capture stdio from echo: FileNotFound
failed command: cd /home/user/code/personal-projects/testingzigbugs/a/doesnt-exist && echo test

#20814 it's not relevant anymore after PR #31205
#20815 it's not relevant anymore after PR #31205
probably #21033 see #21033 (comment)
possibly #21054
probably #21094
#21121 by PR #35711
probably #21133, Debian 13 "Trixie" has been realeased since
#21134 now gives error: error: unable to provide libc for target "wasm32-freestanding-none"
#21139 now gives error: struct layout requires size 409605120000, this compiler implementation supports up to 4294967295
#21216 now gives error: packed structs cannot contain fields of type '*test.P'
#21706 now gives error: use of undefined value here causes illegal behavior
(done) #22214 is fixed by PR #31464
possibly #21332 by PR #32013
#21410
#21434
#21470 by PR #20388, see #21470 (comment)
#21496
#21547
#21583
#21632
#21706 now gives error: use of undefined value here causes illegal behavior
#21709
#24908 contradicts #32009

Some things I noticed:

#3506 doesn't happen in my firefox setup
#4223 needs another issue for the docs part, but the problem expressed in the repro is fixed
#8679 If you add an else statement the problem isn't solved like it says. Perhaps the error is correct (?), so the issue should be closed.
#10408 Vexu's comment doesn't make sense to me. The issue seems to be fixed otherwise.
#21739 gives me error: undefined symbol: switch_context so I can't really test it. Is this a bug?
#18264 the repro works now, without giving an error. Is this intended behavior?
#20187 now gives error: access of union field 'b' while field 'a' is active. Is this intended behavior?
#20825 the repro works now, without giving an error. Is this intended behavior?
#10039 #13713 #17345 #17743 #17792 #20945 you can't get code to repro
In each of these issues: #1908(also probably fixed) #7014 #14466 #15702 #15897 #15972 #16122 #16653 #17715 #17458 #18691 #19356 #19367 #19722 #19994 #20631 #21753 the relevant code seems to be deleted, but I'm not sure it hasn't been moved
#15898 no further discussion after #15898 (comment)
#16195 no response in over 2 years to #16195 (comment)
#16378 no upload in over 2 years like said in #16378 (comment)
#16704 no response in close to 2 years to #16704 (comment)
#16780 no response in close to 3 years to #16780 (comment)
#17517 no response in 2 years and a half to #17517 (comment)
#17718 no update in about 2 years and a half, see the discussion on the issue
#18280 no response in close to a year to #18280 (comment)
#19568 no update in long time #19568 (comment)
#21179 still doesn't have steps to reproduce after #21179 (comment)
#10292 is a duplicate according to #10292 (comment)
#14701 and #14758 are duplicates now
#16019 is a duplicate according to #16019 (comment)
#17551 is a duplicate of #16331 (which is fixed now), according to #17551 (comment)
#18111 is a duplicate, according to #18111 (comment)
#18575 and #18861 are kinda duplicates
#20905 is a duplicate of #19836, according to #20905 (comment)
#22402 is a duplicate according to #22402 (comment)
Are #16382, #16945 #17738 #18417 #18466 #18608 #18681 #18993 #19184 #19338 #19763 #19183 #19996 #20360 #21453 #21657 #21692 planned?
#10644 #13421 #15026 #17008 #17301(now closed) #17358 #17424 #17425 #17529 #17800 #17882 #18126 #18393 #18605 #18888 #18899 #18922 #18929 #18951 #18989 #19242 #19292 #19477 #19511 can be closed similar to how #23636 was closed (unless someone updates the repros) (#19511 is also probably fixed along with being complicated, see #19516 (comment))

TODO (help wanted): look at #17132 #17739 #17785 #17898 #18027 #18065 #18069 #18145 #18388 #18467 #18770 #18871 #19275 #19341 #19492 #19815 #19879 #20021 #20085 #20099 #20258 #20326 #20463 #20519 #20546 #20557 #20586 #20603 #20614 #20701 #20765 #20818 #20846 #20853 #20855 #20930 #20835 #20952 #20976 #20982 #20983 #20984 #20989 #20995 #20996 #21103 #21016 #21142 #21152 #21234 #21308 #21316 #21361 #21492 #21516 #21521 #21551 #21623 #21673 #12781

Also, these issues seem to be fixed and seem to not need tests: - (done) [#576](https://github.com/ziglang/zig/issues/576) - (done) [#747](https://github.com/ziglang/zig/issues/747) - probably [#1487](https://github.com/ziglang/zig/issues/1487) see [#1487 (comment)](https://github.com/ziglang/zig/issues/1487#issuecomment-2566659039) - [#1534](https://github.com/ziglang/zig/issues/1534) by a newer LLVM version - [#1790](https://github.com/ziglang/zig/issues/1790) - [#1882](https://github.com/ziglang/zig/issues/1882) see [#1882 (comment)](https://github.com/ziglang/zig/issues/1882#issuecomment-1716093270) - [#2209](https://github.com/ziglang/zig/issues/2209) - [#2349](https://github.com/ziglang/zig/issues/2349) see [#2349 (comment)](https://github.com/ziglang/zig/issues/2349#issuecomment-1296532312) - [#3125](https://github.com/ziglang/zig/issues/3125) - [#3609](https://github.com/ziglang/zig/issues/3609) now gives error instead of miscompilation - (done) [#3821](https://github.com/ziglang/zig/issues/3821) by a newer LLVM version - [#3884](https://github.com/ziglang/zig/issues/3884) see [#3884 (comment)](https://github.com/ziglang/zig/issues/3884#issuecomment-1013986726d) - [#5191](https://github.com/ziglang/zig/issues/5191) part of [#31131](https://codeberg.org/ziglang/zig/issues/31131) which is resolved - [#5244](https://github.com/ziglang/zig/issues/5244) see [#5244 (comment)](https://github.com/ziglang/zig/issues/5244#issuecomment-2227969602) - [#7354](https://github.com/ziglang/zig/issues/7354) - [#7357](https://github.com/ziglang/zig/issues/7357) has test in `test/behavior/switch.zig` named "switch on pointer type" - [#7774](https://github.com/ziglang/zig/issues/7774) - [#8087](https://github.com/ziglang/zig/issues/8087) std.os.argv is removed by [PR #30644](https://codeberg.org/ziglang/zig/pulls/30644) - [#8997](https://github.com/ziglang/zig/issues/8997) by a newer LLVM version, see [#8997 (comment)](https://github.com/ziglang/zig/issues/8997#issuecomment-1437723601) - [#9215](https://github.com/ziglang/zig/issues/9215) see [#9215 (comment)](https://github.com/ziglang/zig/issues/9215#issuecomment-1480580574) - [#9472](https://github.com/ziglang/zig/issues/9472) see [#9472 (comment)](https://github.com/ziglang/zig/issues/9472#issuecomment-1172978905) - [#9638](https://github.com/ziglang/zig/issues/9638) - [#10185](https://github.com/ziglang/zig/issues/10185) now arrays in `packed struct` gives compiler error - [#10328](https://github.com/ziglang/zig/issues/10328) now gives `error: variable of type 'test.KpcApi__struct_22508' must be const or comptime` - [#10389](https://github.com/ziglang/zig/issues/10389) see [#10389 (comment)](https://github.com/ziglang/zig/issues/10389#issuecomment-1406459954), the duplicate is closed - [#10412](https://github.com/ziglang/zig/issues/10412) see [#10412 (comment)](https://github.com/ziglang/zig/issues/10412#issuecomment-1016945363), the duplicate is closed - [#11367](https://github.com/ziglang/zig/issues/11367) I think this is fixed by [PR #31403](https://codeberg.org/ziglang/zig/pulls/31403) - probably [#12266](https://github.com/ziglang/zig/issues/12266) - [#12344](https://github.com/ziglang/zig/issues/12344) - [#12473](https://github.com/ziglang/zig/issues/12473) (I tested only with the release build of the zig compiler) - [#13123](https://github.com/ziglang/zig/issues/13123) not a problem with the current API - (done) [#13129](https://github.com/ziglang/zig/issues/13129) - [#13509](https://github.com/ziglang/zig/issues/13509) - [#13578](https://github.com/ziglang/zig/issues/13578) now gives `error: dependency loop with length 2` - somewhat [#13807](https://github.com/ziglang/zig/issues/13807) - [#13915](https://github.com/ziglang/zig/issues/13915) see [#13915 (comment)](https://github.com/ziglang/zig/issues/13915#issuecomment-1360813678), Debian 13 "Trixie" has been realeased since - [#14052](https://github.com/ziglang/zig/issues/14052) see [#14052 (comment)](https://github.com/ziglang/zig/issues/14052#issuecomment-1364339978), if not duplicate it needs a test - [#14088](https://github.com/ziglang/zig/issues/14088) see [#14088 (comment)](https://github.com/ziglang/zig/issues/14088#issuecomment-2119018608) - [#14089](https://github.com/ziglang/zig/issues/14089) see [#14089 (comment)](https://github.com/ziglang/zig/issues/14089#issuecomment-1406477673), this is not a bug as labeled - [#14211](https://github.com/ziglang/zig/issues/14211) see [#14211 (comment)](https://github.com/ziglang/zig/issues/14211#issuecomment-1531512507) - [#14318](https://github.com/ziglang/zig/issues/14318) `usingnamespace` has been removed - [#14564](https://github.com/ziglang/zig/issues/14564) now gives `error: asm cannot output to const 'val_low'` - [#14727](https://github.com/ziglang/zig/issues/14727) see [#14727 (comment)](https://github.com/ziglang/zig/issues/14727#issuecomment-1894840763) - [#14873](https://github.com/ziglang/zig/issues/14873) see [#14873 (comment)](https://github.com/ziglang/zig/issues/14873#issuecomment-1861962373) - [#14888](https://github.com/ziglang/zig/issues/14888) see [#14888 (comment)](https://github.com/ziglang/zig/issues/14888#issuecomment-1502435169) - [#14960](https://github.com/ziglang/zig/issues/14960) see [#14960 (comment)](https://github.com/ziglang/zig/issues/14960#issuecomment-2571510849) - [#15154](https://github.com/ziglang/zig/issues/15154) - [#15165](https://github.com/ziglang/zig/issues/15165) repro is to big for a test - probably [#15254](https://github.com/ziglang/zig/issues/15254) - (done) [#15368](https://github.com/ziglang/zig/issues/15368) - [#15504](https://github.com/ziglang/zig/issues/15504) - probably [#15547](https://github.com/ziglang/zig/issues/15547) - [#15601](https://github.com/ziglang/zig/issues/15601) see [#15601 (comment)](https://github.com/ziglang/zig/issues/15601#issuecomment-2597458267) - [#15646](https://github.com/ziglang/zig/issues/15646) unless "this is the kind of thing that can be caught and warned about at build time" from [#15646 (comment)](https://github.com/ziglang/zig/issues/15646#issuecomment-1666903030) - [#15999](https://github.com/ziglang/zig/issues/15999) - [#16343](https://github.com/ziglang/zig/issues/16343) - [#16410](https://github.com/ziglang/zig/issues/16410) not a problem with the current API - probably [#16432](https://github.com/ziglang/zig/issues/16432) based on my little amount of testing - [#16437](https://github.com/ziglang/zig/issues/16437) now gives `error: value in memory does not match slice sentinel` - (done) [#16479](https://github.com/ziglang/zig/issues/16479) - [#16523](https://github.com/ziglang/zig/issues/16523) should be closed or labeled as `error message`, not as `bug` - [#16525](https://github.com/ziglang/zig/issues/16525) see [#16525 (comment)](https://github.com/ziglang/zig/issues/16525#issuecomment-1676293804) - (done) [#16758](https://github.com/ziglang/zig/issues/16758) by a newer LLVM version - [#16775](https://github.com/ziglang/zig/issues/16775) should be closed or labeled as `error message`, not as `bug`; see [#16775 (comment)](https://github.com/ziglang/zig/issues/16775#issuecomment-2661412984) - [#17024](https://github.com/ziglang/zig/issues/17024) because there is [Module.addOptions](https://ziglang.org/documentation/master/std/#std.Build.Module.addOptions) - [#17073](https://github.com/ziglang/zig/issues/17073) now gives `error: type '@EnumLiteral()' does not support field access` - [#17360](https://github.com/ziglang/zig/issues/17360) now gives `error: field bit width does not match earlier field` - [#17401](https://github.com/ziglang/zig/issues/17401) now gives `error: type 'test.MyStruct' depends on itself for alignment query here` - probably [#17515](https://github.com/ziglang/zig/issues/17515) - (done) [#17574](https://github.com/ziglang/zig/issues/17574) now gives `error: packed structs cannot contain fields of type '*const fn () void'` - [#17626](https://github.com/ziglang/zig/issues/17626) see [#17626 (comment)](https://github.com/ziglang/zig/issues/17626#issuecomment-2068210603) - [#17650](https://github.com/ziglang/zig/issues/17650) - (done) [#17676](https://github.com/ziglang/zig/issues/17676) see [#17676 (comment)](https://github.com/ziglang/zig/issues/17676#issuecomment-1774236434) - [#17710](https://github.com/ziglang/zig/issues/17710) see [#17710 (comment)](https://github.com/ziglang/zig/issues/17710#issuecomment-1780918798) - [#17745](https://github.com/ziglang/zig/issues/17745) now gives `General protection exception (no address available)` - [#17775](https://github.com/ziglang/zig/issues/17775) - (done) [#17856](https://github.com/ziglang/zig/issues/17856) now gives `error: packed structs cannot contain fields of type '[*]const u8'` - probably [#17908](https://github.com/ziglang/zig/issues/17908) - probably [#18018](https://github.com/ziglang/zig/issues/18018) - probably [#18050](https://github.com/ziglang/zig/issues/18050) - [#18113](https://github.com/ziglang/zig/issues/18113) now gives `error: unable to resolve comptime value` - [#18147](https://github.com/ziglang/zig/issues/18147) - [#18223](https://github.com/ziglang/zig/issues/18223) now gives `error: unable to perform tail call: compiler backend 'stage2_x86_64' does not support tail calls on target architecture 'x86_64' with the selected CPU feature flags` - [#18263](https://github.com/ziglang/zig/issues/18263) - [#18273](https://github.com/ziglang/zig/issues/18273) now gives `error: error set is discarded` - (done) [#18359](https://github.com/ziglang/zig/issues/18359) - [#18459](https://github.com/ziglang/zig/issues/18459) see [#18459 (comment)](https://github.com/ziglang/zig/issues/18459#issuecomment-1913052428) - [#18495](https://github.com/ziglang/zig/issues/18495) - [#18627](https://github.com/ziglang/zig/issues/18627) see [#18627 (comment)](https://github.com/ziglang/zig/issues/18627#issuecomment-1913052412) - (done) [#18747](https://github.com/ziglang/zig/issues/18747) see [#18747 (comment)](https://github.com/ziglang/zig/issues/18747#issuecomment-1917615419) - probably [#18820](https://github.com/ziglang/zig/issues/18820) - probably [#18830](https://github.com/ziglang/zig/issues/18830) - [#18842](https://github.com/ziglang/zig/issues/18842) - [#18854](https://github.com/ziglang/zig/issues/18854) now gives `error: union field order does not match tag enum field order` - [#18884](https://github.com/ziglang/zig/issues/18884) - [#18928](https://github.com/ziglang/zig/issues/18928) - [#18953](https://github.com/ziglang/zig/issues/18953) - [#18995](https://github.com/ziglang/zig/issues/18995) now gives `panic: integer does not fit in destination type` - [#19011](https://github.com/ziglang/zig/issues/19011) - (done) [#19037](https://github.com/ziglang/zig/issues/19037) - [#19045](https://github.com/ziglang/zig/issues/19045) - [#19098](https://github.com/ziglang/zig/issues/19098) - [#19105](https://github.com/ziglang/zig/issues/19105) - [#19165](https://github.com/ziglang/zig/issues/19165) - [#19209](https://github.com/ziglang/zig/issues/19209) see [#19209 (comment)](https://github.com/ziglang/zig/issues/19209#issuecomment-1983302440) - [#19211](https://github.com/ziglang/zig/issues/19211) now gives `panic: invalid enum value` (maybe it should say `panic: invalid union value`?) - probably [#19369](https://github.com/ziglang/zig/issues/19369) - [#19386](https://github.com/ziglang/zig/issues/19386) - [#19423](https://github.com/ziglang/zig/issues/19423) can be closed or changed to be a doc issue, see [#19423 (comment)](https://github.com/ziglang/zig/issues/19423#issuecomment-3243777543) - [#19443](https://github.com/ziglang/zig/issues/19443) - [#19476](https://github.com/ziglang/zig/issues/19476) superseded by [#30659](https://codeberg.org/ziglang/zig/issues/30659) - [#19578](https://github.com/ziglang/zig/issues/19578) now gives `error: non-scalar sentinel type 'example.Code'` - probably [#19685](https://github.com/ziglang/zig/issues/19685) - probably [#19870](https://github.com/ziglang/zig/issues/19870) (also [PR #19871](https://github.com/ziglang/zig/pull/19871) should be closed) - [#19935](https://github.com/ziglang/zig/issues/19935) was fixed in `0.15.1` - [#19979](https://github.com/ziglang/zig/issues/19979) fixed in [PR #21755](https://github.com/ziglang/zig/pull/21755) (any further issue is covered by [#1516](https://github.com/ziglang/zig/issues/1516), see [#19979 (comment)](https://github.com/ziglang/zig/issues/19979#issuecomment-2116322745)) - [#20016](https://github.com/ziglang/zig/issues/20016) - [#20067](https://github.com/ziglang/zig/issues/20067) `errdefer |err|` has been removed in [PR #32130](https://codeberg.org/ziglang/zig/pulls/32130) - [#20076](https://github.com/ziglang/zig/issues/20076) - [#20079](https://github.com/ziglang/zig/issues/20079) - [#20154](https://github.com/ziglang/zig/issues/20154) now gives `error: parameter of type 'noreturn' not allowed` and has already a test case - [#20208](https://github.com/ziglang/zig/issues/20208) - [#20221](https://github.com/ziglang/zig/issues/20221) now gives more notes - [#20320](https://github.com/ziglang/zig/issues/20320) - [#20332](https://github.com/ziglang/zig/issues/20332) - [#20347](https://github.com/ziglang/zig/issues/20347) - [#20369](https://github.com/ziglang/zig/issues/20369) `errdefer |err|` has been removed in [PR #32130](https://codeberg.org/ziglang/zig/pulls/32130) - probably [#20406](https://github.com/ziglang/zig/issues/20406) @alexrp Can you confirm this? - possibly [#20453](https://github.com/ziglang/zig/issues/20453) because now gives `error: expected type '[5]@Vector(5, usize)', found '[5][5]usize'` - probably [#20458](https://github.com/ziglang/zig/issues/20458) - [#20461](https://github.com/ziglang/zig/issues/20461) now gives a note along with error: `Main.zig:1:1: note: declared here const Point2D = @import("Point.zig").Point;` - [#20501](https://github.com/ziglang/zig/issues/20501) (at least with `doas` instead of `sudo`) - [#20505](https://github.com/ziglang/zig/issues/20505) due to commit https://codeberg.org/ziglang/zig/commit/c895aa7a35b178576b89e600a20af9d16da36dea - [#20524](https://github.com/ziglang/zig/issues/20524) I believe does not apply anymore - [#20539](https://github.com/ziglang/zig/issues/20539) by [PR #31403](https://codeberg.org/ziglang/zig/pulls/31403) - [#20562](https://github.com/ziglang/zig/issues/20562) - [#20566](https://github.com/ziglang/zig/issues/20566) now gives `error: reached unreachable code` - [#20601](https://github.com/ziglang/zig/issues/20601) is fixed, but sometimes gives a error that I presume it's already known: ``` error: sub-compilation of compiler_rt failed note: failed to check cache: '/home/user/.zig-master/lib/compiler_rt.zig' file_hash FileNotFound ``` - probably [#20606](https://github.com/ziglang/zig/issues/20606) - probably [#20612](https://github.com/ziglang/zig/issues/20612) - probably [#20665](https://github.com/ziglang/zig/issues/20665) - probably [#20676](https://github.com/ziglang/zig/issues/20676) - [#20680](https://github.com/ziglang/zig/issues/20680) - [#20752](https://github.com/ziglang/zig/issues/20752) now gives `error: expected type 'test.Range', found 'struct { usize, usize }'` - [#20793](https://github.com/ziglang/zig/issues/20793) now gives: ``` error: failed to spawn and capture stdio from echo: FileNotFound failed command: cd /home/user/code/personal-projects/testingzigbugs/a/doesnt-exist && echo test ``` - [#20814](https://github.com/ziglang/zig/issues/20814) it's not relevant anymore after [PR #31205](https://codeberg.org/ziglang/zig/pulls/31205) - [#20815](https://github.com/ziglang/zig/issues/20815) it's not relevant anymore after [PR #31205](https://codeberg.org/ziglang/zig/pulls/31205) - probably [#21033](https://github.com/ziglang/zig/issues/21033) see [#21033 (comment)](https://github.com/ziglang/zig/issues/21033#issuecomment-3369225232) - possibly [#21054](https://github.com/ziglang/zig/issues/21054) - probably [#21094](https://github.com/ziglang/zig/issues/21094) - [#21121](https://github.com/ziglang/zig/issues/21121) by [PR #35711](https://codeberg.org/ziglang/zig/pulls/35711) - probably [#21133](https://github.com/ziglang/zig/issues/21133), Debian 13 "Trixie" has been realeased since - [#21134](https://github.com/ziglang/zig/issues/21134) now gives `error: error: unable to provide libc for target "wasm32-freestanding-none"` - [#21139](https://github.com/ziglang/zig/issues/21139) now gives `error: struct layout requires size 409605120000, this compiler implementation supports up to 4294967295` - [#21216](https://github.com/ziglang/zig/issues/21216) now gives `error: packed structs cannot contain fields of type '*test.P'` - [#21706](https://github.com/ziglang/zig/issues/21706) now gives `error: use of undefined value here causes illegal behavior` - (done) [#22214](https://github.com/ziglang/zig/issues/22214) is fixed by [PR #31464](https://codeberg.org/ziglang/zig/pulls/31464) - possibly [#21332](https://github.com/ziglang/zig/issues/21332) by [PR #32013](https://codeberg.org/ziglang/zig/pulls/32013) - [#21410](https://github.com/ziglang/zig/issues/21410) - [#21434](https://github.com/ziglang/zig/issues/21434) - [#21470](https://github.com/ziglang/zig/issues/21470) by [PR #20388](https://github.com/ziglang/zig/pull/20388), see [#21470 (comment)](https://github.com/ziglang/zig/issues/21470#issuecomment-2364998282) - [#21496](https://github.com/ziglang/zig/issues/21496) - [#21547](https://github.com/ziglang/zig/issues/21547) - [#21583](https://github.com/ziglang/zig/issues/21583) - [#21632](https://github.com/ziglang/zig/issues/21632) - [#21706](https://github.com/ziglang/zig/issues/21706) now gives `error: use of undefined value here causes illegal behavior` - [#21709](https://github.com/ziglang/zig/issues/21709) - [#24908](https://github.com/ziglang/zig/issues/24908) contradicts [#32009](https://codeberg.org/ziglang/zig/issues/32009) Some things I noticed: - [#3506](https://github.com/ziglang/zig/issues/3506) doesn't happen in my firefox setup - [#4223](https://github.com/ziglang/zig/issues/4223) needs another issue for the docs part, but the problem expressed in the repro is fixed - [#8679](https://github.com/ziglang/zig/issues/8679) If you add an else statement the problem isn't solved like it says. Perhaps the error is correct (?), so the issue should be closed. - [#10408](https://github.com/ziglang/zig/issues/10408) Vexu's comment doesn't make sense to me. The issue seems to be fixed otherwise. - [#21739](https://github.com/ziglang/zig/issues/21739) gives me `error: undefined symbol: switch_context` so I can't really test it. Is this a bug? - [#18264](https://github.com/ziglang/zig/issues/18264) the repro works now, without giving an error. Is this intended behavior? - [#20187](https://github.com/ziglang/zig/issues/20187) now gives `error: access of union field 'b' while field 'a' is active`. Is this intended behavior? - [#20825](https://github.com/ziglang/zig/issues/20825) the repro works now, without giving an error. Is this intended behavior? - [#10039](https://github.com/ziglang/zig/issues/10039) [#13713](https://github.com/ziglang/zig/issues/13713) [#17345](https://github.com/ziglang/zig/issues/17345) [#17743](https://github.com/ziglang/zig/issues/17743) [#17792](https://github.com/ziglang/zig/issues/17792) [#20945](https://github.com/ziglang/zig/issues/20945) you can't get code to repro - In each of these issues: [#1908](https://github.com/ziglang/zig/issues/1908)(also probably fixed) [#7014](https://github.com/ziglang/zig/issues/7014) [#14466](https://github.com/ziglang/zig/issues/14466) [#15702](https://github.com/ziglang/zig/issues/15702) [#15897](https://github.com/ziglang/zig/issues/15897) [#15972](https://github.com/ziglang/zig/issues/15972) [#16122](https://github.com/ziglang/zig/issues/16122) [#16653](https://github.com/ziglang/zig/issues/16653) [#17715](https://github.com/ziglang/zig/issues/17715) [#17458](https://github.com/ziglang/zig/issues/17458) [#18691](https://github.com/ziglang/zig/issues/18691) [#19356](https://github.com/ziglang/zig/issues/19356) [#19367](https://github.com/ziglang/zig/issues/19367) [#19722](https://github.com/ziglang/zig/issues/19722) [#19994](https://github.com/ziglang/zig/issues/19994) [#20631](https://github.com/ziglang/zig/issues/20631) [#21753](https://github.com/ziglang/zig/issues/21753) the relevant code seems to be deleted, but I'm not sure it hasn't been moved - [#15898](https://github.com/ziglang/zig/issues/15898) no further discussion after [#15898 (comment)](https://github.com/ziglang/zig/issues/15898#issuecomment-2603678590) - [#16195](https://github.com/ziglang/zig/issues/16195) no response in over 2 years to [#16195 (comment)](https://github.com/ziglang/zig/issues/16195#issuecomment-1916552748) - [#16378](https://github.com/ziglang/zig/issues/16378) no upload in over 2 years like said in [#16378 (comment)](https://github.com/ziglang/zig/issues/16378#issuecomment-1712175710) - [#16704](https://github.com/ziglang/zig/issues/16704) no response in close to 2 years to [#16704 (comment)](https://github.com/ziglang/zig/issues/16704#issuecomment-2316558524) - [#16780](https://github.com/ziglang/zig/issues/16780) no response in close to 3 years to [#16780 (comment)](https://github.com/ziglang/zig/issues/16780#issuecomment-1677020742) - [#17517](https://github.com/ziglang/zig/issues/17517) no response in 2 years and a half to [#17517 (comment)](https://github.com/ziglang/zig/issues/17517#issuecomment-1762550633) - [#17718](https://github.com/ziglang/zig/issues/17718) no update in about 2 years and a half, see the discussion on the issue - [#18280](https://github.com/ziglang/zig/issues/18280) no response in close to a year to [#18280 (comment)](https://github.com/ziglang/zig/issues/18280#issuecomment-2912420516) - [#19568](https://github.com/ziglang/zig/issues/19568) no update in long time [#19568 (comment)](https://github.com/ziglang/zig/issues/19568#issuecomment-2041223529) - [#21179](https://github.com/ziglang/zig/issues/21179) still doesn't have steps to reproduce after [#21179 (comment)](https://github.com/ziglang/zig/issues/21179#issuecomment-2308131906) - [#10292](https://github.com/ziglang/zig/issues/10292) is a duplicate according to [#10292 (comment)](https://github.com/ziglang/zig/issues/10292#issuecomment-2336994805) - [#14701](https://github.com/ziglang/zig/issues/14701) and [#14758](https://github.com/ziglang/zig/issues/14758) are duplicates now - [#16019](https://github.com/ziglang/zig/issues/16019) is a duplicate according to [#16019 (comment)](https://github.com/ziglang/zig/issues/16019#issuecomment-2221273986) - [#17551](https://github.com/ziglang/zig/issues/17551) is a duplicate of [#16331](https://github.com/ziglang/zig/issues/16331) (which is fixed now), according to [#17551 (comment)](https://github.com/ziglang/zig/issues/17551#issuecomment-1764618888) - [#18111](https://github.com/ziglang/zig/issues/18111) is a duplicate, according to [#18111 (comment)](https://github.com/ziglang/zig/issues/18111#issuecomment-1826252863) - [#18575](https://github.com/ziglang/zig/issues/18575) and [#18861](https://github.com/ziglang/zig/issues/18861) are kinda duplicates - [#20905](https://github.com/ziglang/zig/issues/20905) is a duplicate of [#19836](https://github.com/ziglang/zig/issues/19836), according to [#20905 (comment)](https://github.com/ziglang/zig/issues/20905#issuecomment-2994454258) - [#22402](https://github.com/ziglang/zig/issues/22402) is a duplicate according to [#22402 (comment)](https://github.com/ziglang/zig/issues/22402#issuecomment-2570642528) - Are [#16382](https://github.com/ziglang/zig/issues/16382), [#16945](https://github.com/ziglang/zig/issues/16945) [#17738](https://github.com/ziglang/zig/issues/17738) [#18417](https://github.com/ziglang/zig/issues/18417) [#18466](https://github.com/ziglang/zig/issues/18466) [#18608](https://github.com/ziglang/zig/issues/18608) [#18681](https://github.com/ziglang/zig/issues/18681) [#18993](https://github.com/ziglang/zig/issues/18993) [#19184](https://github.com/ziglang/zig/issues/19184) [#19338](https://github.com/ziglang/zig/issues/19338) [#19763](https://github.com/ziglang/zig/issues/19763) [#19183](https://github.com/ziglang/zig/issues/19183) [#19996](https://github.com/ziglang/zig/issues/19996) [#20360](https://github.com/ziglang/zig/issues/20360) [#21453](https://github.com/ziglang/zig/issues/21453) [#21657](https://github.com/ziglang/zig/issues/21657) [#21692](https://github.com/ziglang/zig/issues/21692) planned? - [#10644](https://github.com/ziglang/zig/issues/10644) [#13421](https://github.com/ziglang/zig/issues/13421) [#15026](https://github.com/ziglang/zig/issues/15026) [#17008](https://github.com/ziglang/zig/issues/17008) [#17301](https://github.com/ziglang/zig/issues/17301)(now closed) [#17358](https://github.com/ziglang/zig/issues/17358) [#17424](https://github.com/ziglang/zig/issues/17424) [#17425](https://github.com/ziglang/zig/issues/17425) [#17529](https://github.com/ziglang/zig/issues/17529) [#17800](https://github.com/ziglang/zig/issues/17800) [#17882](https://github.com/ziglang/zig/issues/17882) [#18126](https://github.com/ziglang/zig/issues/18126) [#18393](https://github.com/ziglang/zig/issues/18393) [#18605](https://github.com/ziglang/zig/issues/18605) [#18888](https://github.com/ziglang/zig/issues/18888) [#18899](https://github.com/ziglang/zig/issues/18899) [#18922](https://github.com/ziglang/zig/issues/18922) [#18929](https://github.com/ziglang/zig/issues/18929) [#18951](https://github.com/ziglang/zig/issues/18951) [#18989](https://github.com/ziglang/zig/issues/18989) [#19242](https://github.com/ziglang/zig/issues/19242) [#19292](https://github.com/ziglang/zig/issues/19292) [#19477](https://github.com/ziglang/zig/issues/19477) [#19511](https://github.com/ziglang/zig/issues/19511) can be closed similar to how [#23636](https://github.com/ziglang/zig/issues/23636) was closed (unless someone updates the repros) ([#19511](https://github.com/ziglang/zig/issues/19511) is also probably fixed along with being complicated, see [#19516 (comment)](https://github.com/ziglang/zig/issues/19516#issuecomment-2034180164)) TODO (help wanted): look at [#17132](https://github.com/ziglang/zig/issues/17132) [#17739](https://github.com/ziglang/zig/issues/17739) [#17785](https://github.com/ziglang/zig/issues/17785) [#17898](https://github.com/ziglang/zig/issues/17898) [#18027](https://github.com/ziglang/zig/issues/18027) [#18065](https://github.com/ziglang/zig/issues/18065) [#18069](https://github.com/ziglang/zig/issues/18069) [#18145](https://github.com/ziglang/zig/issues/18145) [#18388](https://github.com/ziglang/zig/issues/18388) [#18467](https://github.com/ziglang/zig/issues/18467) [#18770](https://github.com/ziglang/zig/issues/18770) [#18871](https://github.com/ziglang/zig/issues/18871) [#19275](https://github.com/ziglang/zig/issues/19275) [#19341](https://github.com/ziglang/zig/issues/19341) [#19492](https://github.com/ziglang/zig/issues/19492) [#19815](https://github.com/ziglang/zig/issues/19815) [#19879](https://github.com/ziglang/zig/issues/19879) [#20021](https://github.com/ziglang/zig/issues/20021) [#20085](https://github.com/ziglang/zig/issues/20085) [#20099](https://github.com/ziglang/zig/issues/20099) [#20258](https://github.com/ziglang/zig/issues/20259) [#20326](https://github.com/ziglang/zig/issues/20326) [#20463](https://github.com/ziglang/zig/issues/20463) [#20519](https://github.com/ziglang/zig/issues/20519) [#20546](https://github.com/ziglang/zig/issues/20546) [#20557](https://github.com/ziglang/zig/issues/20557) [#20586](https://github.com/ziglang/zig/issues/20586) [#20603](https://github.com/ziglang/zig/issues/20603) [#20614](https://github.com/ziglang/zig/issues/20614) [#20701](https://github.com/ziglang/zig/issues/20701) [#20765](https://github.com/ziglang/zig/issues/20765) [#20818](https://github.com/ziglang/zig/issues/20818) [#20846](https://github.com/ziglang/zig/issues/20846) [#20853](https://github.com/ziglang/zig/issues/20853) [#20855](https://github.com/ziglang/zig/issues/20855) [#20930](https://github.com/ziglang/zig/issues/20930) [#20835](https://github.com/ziglang/zig/issues/20935) [#20952](https://github.com/ziglang/zig/issues/20952) [#20976](https://github.com/ziglang/zig/issues/20976) [#20982](https://github.com/ziglang/zig/issues/20982) [#20983](https://github.com/ziglang/zig/issues/20983) [#20984](https://github.com/ziglang/zig/issues/20984) [#20989](https://github.com/ziglang/zig/issues/20989) [#20995](https://github.com/ziglang/zig/issues/20995) [#20996](https://github.com/ziglang/zig/issues/20996) [#21103](https://github.com/ziglang/zig/issues/21103) [#21016](https://github.com/ziglang/zig/issues/21016) [#21142](https://github.com/ziglang/zig/issues/21142) [#21152](https://github.com/ziglang/zig/issues/21152) [#21234](https://github.com/ziglang/zig/issues/21234) [#21308](https://github.com/ziglang/zig/issues/21308) [#21316](https://github.com/ziglang/zig/issues/21316) [#21361](https://github.com/ziglang/zig/issues/21361) [#21492](https://github.com/ziglang/zig/issues/21492) [#21516](https://github.com/ziglang/zig/issues/21516) [#21521](https://github.com/ziglang/zig/issues/21521) [#21551](https://github.com/ziglang/zig/issues/21551) [#21623](https://github.com/ziglang/zig/issues/21623) [#21673](https://github.com/ziglang/zig/issues/21673) [#12781](https://github.com/ziglang/zig/issues/21781)

❤️ 1

K4 commented

2026年03月25日 16:32:26 +01:00

Author

Contributor

Copy link

#3064
#3065
#3069
#3074
#3078
#3160
#3656
#3777
#3831
#4060
#4061
#4063
#4188
#4728
#4729
#4730
#4885
(done) #4974
#5258
#5509
#5604
#5706
#6135
#6590
#7070
#7793
#7902
#7995
#8001
#8648
#8654
#8666
#8672
#8907
#9397
#9569
#9719
#10343
#10484
#10622
#10623
#10735
#11644
#11796
#13359
#13397
#15538

@andrewrk @mlugg There are a lot of issues related to the old implementation of async code (before the self-hosted compiler). Are these still relevant? Maybe some are some aren't. Here is a list of them: - [#3064](https://github.com/ziglang/zig/issues/3064) - [#3065](https://github.com/ziglang/zig/issues/3065) - [#3069](https://github.com/ziglang/zig/issues/3069) - [#3074](https://github.com/ziglang/zig/issues/3074) - [#3078](https://github.com/ziglang/zig/issues/3078) - [#3160](https://github.com/ziglang/zig/issues/3160) - [#3656](https://github.com/ziglang/zig/issues/3656) - [#3777](https://github.com/ziglang/zig/issues/3777) - [#3831](https://github.com/ziglang/zig/issues/3831) - [#4060](https://github.com/ziglang/zig/issues/4060) - [#4061](https://github.com/ziglang/zig/issues/4061) - [#4063](https://github.com/ziglang/zig/issues/4063) - [#4188](https://github.com/ziglang/zig/issues/4188) - [#4728](https://github.com/ziglang/zig/issues/4728) - [#4729](https://github.com/ziglang/zig/issues/4729) - [#4730](https://github.com/ziglang/zig/issues/4730) - [#4885](https://github.com/ziglang/zig/issues/4885) - (done) [#4974](https://github.com/ziglang/zig/issues/4974) - [#5258](https://github.com/ziglang/zig/issues/5258) - [#5509](https://github.com/ziglang/zig/issues/5509) - [#5604](https://github.com/ziglang/zig/issues/5604) - [#5706](https://github.com/ziglang/zig/issues/5706) - [#6135](https://github.com/ziglang/zig/issues/6135) - [#6590](https://github.com/ziglang/zig/issues/6590) - [#7070](https://github.com/ziglang/zig/issues/7070) - [#7793](https://github.com/ziglang/zig/issues/7793) - [#7902](https://github.com/ziglang/zig/issues/7902) - [#7995](https://github.com/ziglang/zig/issues/7995) - [#8001](https://github.com/ziglang/zig/issues/8001) - [#8648](https://github.com/ziglang/zig/issues/8648) - [#8654](https://github.com/ziglang/zig/issues/8654) - [#8666](https://github.com/ziglang/zig/issues/8666) - [#8672](https://github.com/ziglang/zig/issues/8672) - [#8907](https://github.com/ziglang/zig/issues/8907) - [#9397](https://github.com/ziglang/zig/issues/9379) - [#9569](https://github.com/ziglang/zig/issues/9569) - [#9719](https://github.com/ziglang/zig/issues/9719) - [#10343](https://github.com/ziglang/zig/issues/10343) - [#10484](https://github.com/ziglang/zig/issues/10484) - [#10622](https://github.com/ziglang/zig/issues/10622) - [#10623](https://github.com/ziglang/zig/issues/10623) - [#10735](https://github.com/ziglang/zig/issues/10735) - [#11644](https://github.com/ziglang/zig/issues/11644) - [#11796](https://github.com/ziglang/zig/issues/11796) - [#13359](https://github.com/ziglang/zig/issues/13359) - [#13397](https://github.com/ziglang/zig/issues/13397) - [#15538](https://github.com/ziglang/zig/issues/15538)

K4 referenced this issue

2026年04月07日 16:23:49 +02:00

Add test for comptime-only fuctions #31776

alexrp added the

contributor-friendly

testing

labels

2026年04月08日 05:13:43 +02:00

K4 referenced this issue

2026年04月08日 09:09:07 +02:00

Add test for comptime-only fuctions #31776

mimshipio commented

2026年04月14日 15:48:59 +02:00

Copy link

#16613 seems to be solved
#16106 seems to be solved

I took the code from the original issues and put them in tests, if I did something wrong please let me know.

[#16613](https://github.com/ziglang/zig/issues/16613) seems to be solved [#16106](https://github.com/ziglang/zig/issues/16106) seems to be solved I took the code from the original issues and put them in tests, if I did something wrong please let me know.

16106.zig

169 B

16613.zig

1.4 KiB

K4 commented

2026年04月14日 16:02:54 +02:00

Author

Contributor

Copy link

Yes, there are solved, but they need tests to be closed. These issues are already tracked by this issue.
You can make a pull request with your tests.
If you would like to try to find solved issues, please look at the TODO from my first comment to this issue.

Yes, there are solved, but they need tests to be closed. These issues are already tracked by this issue. You can make a pull request with your tests. If you would like to try to find solved issues, please look at the TODO from my first comment to this issue.

ej-shafran commented

2026年04月20日 23:25:13 +02:00

Contributor

Copy link

Adding a comment here since it seems like the most relevant place.

Wanted to help out so I added a simple test for #5174, and it seems to crash the complier (at least on my machine)!

What should I do (and, generally, what should anyone do if they discover that one of these issues isn't fully closed or still causes problems)? Do I open a new issue (this crash seems to be different from the assertion failure that the original issue mentions)?

I can try and resolve the issue, but I feel like it's probably more useful to discuss what the issue is and how it might be resolved (maybe a compiler error, or some other user-facing assertion that provides better developer experience). So I'd love to know where/how to report this, and in the meanwhile I'll try to help with some of the other issues listed here.

Adding a comment here since it seems like the most relevant place. Wanted to help out so I added a simple test for [#5174](https://github.com/ziglang/zig/issues/5174), and it seems to crash the complier (at least on my machine)! What should I do (and, generally, what should anyone do if they discover that one of these issues isn't fully closed or still causes problems)? Do I open a new issue (this crash seems to be different from the assertion failure that the original issue mentions)? I can try and resolve the issue, but I feel like it's probably more useful to discuss what the issue is and how it might be resolved (maybe a compiler error, or some other user-facing assertion that provides better developer experience). So I'd love to know where/how to report this, and in the meanwhile I'll try to help with some of the other issues listed here.

K4 commented

2026年04月21日 18:42:48 +02:00

Author

Contributor

Copy link

My machine is x86_64-linux, so maybe #5174 crashes if you have a different one.

In general, if you find an issue from the list that isn't solved, you should make a comment on this issue explaining why it's not solved. I'm not qualified to fully answer your question, since I'm not in zig's core team. cc @alexrp

My machine is `x86_64-linux`, so maybe [#5174](https://github.com/ziglang/zig/issues/5174) crashes if you have a different one. In general, if you find an issue from the list that isn't solved, you should make a comment on this issue explaining why it's not solved. I'm not qualified to fully answer your question, since I'm not in zig's core team. cc @alexrp

K4 commented

2026年04月26日 14:39:54 +02:00

Author

Contributor

Copy link

I see that lately there were a lot of issues closed, some being listed here. To not duplicate work, someone in the zig's core team should close issues in bulk from my first two comments, even if there are still a lot of issues remaiding to be looked at.

alexrp commented

2026年04月26日 14:42:45 +02:00

Owner

Copy link

@ej-shafran wrote in #31661 (comment):

What should I do (and, generally, what should anyone do if they discover that one of these issues isn't fully closed or still causes problems)? Do I open a new issue (this crash seems to be different from the assertion failure that the original issue mentions)?

We consider GitHub issues copy-on-write, i.e. you should open a new issue on Codeberg that links back to the GitHub one, and continue the discussion there.

@K4 wrote in #31661 (comment):

I see that lately there were a lot of issues closed, some being listed here. To not duplicate work, someone in the zig's core team should close issues in bulk from my first two comments, even if there are still a lot of issues remaiding to be looked at.

To be clear, I was just going over old arch-specific issues on GitHub, not this list in particular. I like to do this after every LLVM upgrade since many are often resolved upstream.

@ej-shafran wrote in https://codeberg.org/ziglang/zig/issues/31661#issuecomment-13396317: > What should I do (and, generally, what should anyone do if they discover that one of these issues isn't fully closed or still causes problems)? Do I open a new issue (this crash seems to be different from the assertion failure that the original issue mentions)? We consider GitHub issues copy-on-write, i.e. you should open a new issue on Codeberg that links back to the GitHub one, and continue the discussion there. @K4 wrote in https://codeberg.org/ziglang/zig/issues/31661#issuecomment-13785374: > I see that lately there were a lot of issues closed, some being listed here. To not duplicate work, someone in the zig's core team should close issues in bulk from my first two comments, even if there are still a lot of issues remaiding to be looked at. To be clear, I was just going over old arch-specific issues on GitHub, not this list in particular. I like to do this after every LLVM upgrade since many are often resolved upstream.

K4 commented

2026年04月26日 15:25:40 +02:00

Author

Contributor

Copy link

@alexrp wrote in #31661 (comment):

To be clear, I was just going over old arch-specific issues on GitHub, not this list in particular.

I know this.
What I was saying is that both you and I found that some issues are resolved, thus duplicating work.

@alexrp wrote in [#31661 (comment)](https://codeberg.org/ziglang/zig/issues/31661#issuecomment-13785440): > To be clear, I was just going over old arch-specific issues on GitHub, not this list in particular. I know this. What I was saying is that both you and I found that some issues are resolved, thus duplicating work.

K4 referenced this issue

2026年05月19日 20:09:37 +02:00

add test for linking lib with obj and exe with obj #35357

ej-shafran referenced this issue

2026年05月23日 21:41:23 +02:00

Legacy issue test for #5293 #35434

ej-shafran referenced this issue

2026年05月23日 22:04:53 +02:00

Legacy issue regarding comptime std.fmt.bufPrint (#5401) #35435

ej-shafran referenced this issue

2026年05月23日 22:23:26 +02:00

Legacy issue regarding runtime operation in comptime scope (#5458) #35436

ej-shafran referenced this issue

2026年05月23日 22:33:36 +02:00

Legacy issue test for #6076 #35437

No Branch/Tag specified

Branches Tags

master

elfv2

spork8

restricted

0.16.x

panic-rewrite

parking-futex-lockfree

windows-Io-cleanup

Io-watch

ParseCommandLineOptions

windows-async-files

poll-ring

debug-file-leaks-differently

debug-file-leaks

ProcessPrng

elfv2-dyn

jobserver

threadtheft

io-threaded-no-queue

0.15.x

Io.net

comptime-allocator

restricted-function-pointers

cli

wasm-linker-writer

wrangle-writer-buffering

sha1-stream

async-await-demo

fixes

0.14.x

ast-node-methods

macos-debug-info

make-vs-configure

fuzz-macos

sans-aro

ArrayList-reserve

incr-bug

llvm-ir-nosanitize-metadata

ci-tarballs

ci-scripts

threadpool

0.12.x

new-pkg-hash

json-diagnostics

more-doctests

rework-comptime-mutation

0.11.x

ci-perf-comment

stage2-async

0.10.x

autofix

0.9.x

aro

hcs

0.8.x

0.7.x

Labels

Clear labels

This proposal is planned.

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

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

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.

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

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

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#31661

No description provided.

Delete branch "%!s()"

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?