←back to thread

Open-source Zig book

(www.zigbook.net)
692 points rudedogg | 2 comments | 16 Nov 25 19:44 UTC | HN request time: 0.48s | source
Show context
rudedogg ◴[17 Nov 25 10:42 UTC] No.45952436[source]▶
I submitted this and unfortunately it is likely AI generated. The authors github history suggests it at the very least, along with seemingly misunderstanding a reference to a Zig language feature (labeled blocks - https://zig.guide/language-basics/labelled-blocks/) in the project issues (https://github.com/zigbook/zigbook/issues/4).

I’m not sure how much value is to be had here, and it’s unfortunate the author wasn’t honest about how it was created.

I wish I wouldn’t have submitted this so quickly but I was excited about the new resource and the chapters I dug into looked good and accurate.

I worry about whether this will be maintained, if there are hallucinations, and if it’s worth investing time into.

replies(13): >>45952561 #>>45952581 #>>45952667 #>>45952728 #>>45952742 #>>45952869 #>>45953014 #>>45953055 #>>45953161 #>>45953533 #>>45953660 #>>45956501 #>>45969184 #
1. CraftingLinks ◴[17 Nov 25 12:02 UTC] No.45952869[source]▶
I looked into that project issue your referencing. There is absolutely zero mentioning of zig labeled blocks in that exchange. There is no misunderstanding or confusion whatsoever.
replies(1): >>45953954 #
2. jasonjmcghee ◴[17 Nov 25 14:37 UTC] No.45953954[source]▶
It's a formatting bug with zig labeled blocks and the response was a screenshot of code without one, saying (paraphrasing) lgtm it must be on your end.

See the first screenshot in the exchange with newlines breaking up the label and block - and maybe this for proper formatting https://zig.guide/language-basics/labelled-blocks/