←back to thread

Open-source Zig book

(www.zigbook.net)
692 points rudedogg | 1 comments | | HN request time: 0s | source
Show context
rudedogg ◴[] 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 #
cryptocod3 ◴[] No.45952581[source]
> if there are hallucinations

Plenty. I assumed that the code examples had been cleaned up manually, so instead I looked at a few random "Caveats, alternatives, edge cases" sections. These contain errors typically made by LLMs, such as suggesting to use features that doesn't exist (std.mem.terminated), are non-public (argvToScriptCommandLineWindows) or removed (std.BoundedArray). These sections also surfaces irrelevant stdlib and compiler implementation details.

replies(2): >>45952750 #>>45953367 #
1. ◴[] No.45953367[source]