bizarre zig compilation error on commented out Go code in zig src file

[zigster64]

This is a good one, and quite funny !

0.14.0-dev.823+624fa8523 on Mac intel. Don't know if Mac arm64 has the same issue yet.

src/datetime.zig:1007:2: error: expected statement, found 'invalid token'
// us := rand.Int63n(31536000000000000)

same thing happens in web socket lib

handshake.zig:55:5: error: expected statement, found 'invalid token'
// Connection: keep-alive, Upgrade

Not a problem with your code, but ... looks like its uncovered an interesting compiler bug.

At first I thought it might be the incompatible Go code in a comment tripping up sema, but on closer inspection, looks like its the presence of a colon in a comment.

Working on a patch to Zig to fix :)

[karlseguin]

Had karlseguin/websocket.zig#40 on websocket.zig re tab in a comment this morning.

[zigster64]

oh - its a tab in a comment ?

that's weird. ok thanks. Still a zig bug then - good catch (ok, not a zig bug after reading the linked issue - Andy really doesn't like his tabs, hey. Looks like zig fmt and no tabs till be a thing we will have to live with long term. Spec conformance - fair enough)

Yeah, can't reproduce with a simple test app with commented out Go code

[karlseguin]

ziglang/zig#20885

ziglang/zig-spec#38

This is the new reality I guess.