zlacker

[return to "Zig Libc"]
1. nemo16+EV[view] [source] 2026-02-02 21:52:36
>>ingve+(OP)
This strikes me as a very agent-friendly problem. Given a harness that enforces sufficiently-rigorous tests, I'm sure you could spin up an agent loop that methodically churns through these functions one by one, finishing in a few days.
◧◩
2. hennin+W11[view] [source] 2026-02-02 22:15:00
>>nemo16+EV
Have you ever used an LLM with Zig? It will generate syntactically invalid code. Zig breaks so often and LLMs have such an eternally old knowledge cutoff that they only know old ass broken versions.

The same goes for TLA+ and all the other obscure things people think would be great to use with LLMs, and they would, if there was as much training data as there was for JavaScript and Python.

◧◩◪
3. Grazia+1f1[view] [source] 2026-02-02 23:00:45
>>hennin+W11
You must have not tried this with an LLM agent in the past few months.
◧◩◪◨
4. ale+mw1[view] [source] 2026-02-03 00:25:36
>>Grazia+1f1
i tested sonnet 4.5 just last week on a zig codebase and it has to be instructed the std.ArrayList syntax every time.
◧◩◪◨⬒
5. rudedo+UO1[view] [source] 2026-02-03 02:27:13
>>ale+mw1
I made a Zig agent skill yesterday if interested: https://github.com/rudedogg/zig-skills/

Claude getting the ArrayList API wrong every time was a major reason why

It’s AI generated but should help. I need to test and review it more (noticed it mentions async which isn’t in 0.15.x :| )

◧◩◪◨⬒⬓
6. ale+ih3[view] [source] 2026-02-03 14:14:25
>>rudedo+UO1
Fighting fire with fire
◧◩◪◨⬒⬓⬔
7. rudedo+mA4[view] [source] 2026-02-03 19:48:25
>>ale+ih3
A little bit! I wrote a long blog post about how I made it, I think the strategy of having an LLM look at individual std modules one by one make it actually pretty accurate. Not perfect, but better than I expected
[go to top]