I commented two issues in total, but my comments were deleted so I can only say from memory what I wrote.
1I said that is is suspect that on fresh zig project watch mode watches 77 folders (very likely zig source that should not change)
I wrote the suggestion for simpler error message, and also suggested a hint would be nice for such case so noobs like me could understand what was the problem possibly without usin LLM.
I am using LLM to learn ZIG, but looking into where LLM helps me and if things can be improved so ppl need LLM less.
I took time understand the error (I was trying to print a error union with number with number format) I am a noob, so yes I need LLM for such simple thing.
I did go through all ziglins code without LLM, but it was not enough to get used to the syntax.
I can understand strict stance for LLM generated issues or LLM generated comments, it would be unproductive to punish someone for using LLM to learn ZIG.
My best advice is to not comment or suggest change for Zig itself using LLM at all. The policy is to silently block people and I don’t think it’s likely to change any time soon. I don’t agree with it, the silent part makes it unrespectful, but it is what it is.
Enjoy Zig as a user, write programs with it, just don’t get involved with Zig development until you can do it completely without LLM.
I did not generate comment with LLM, I made a comment manually, after LLM helped me find the issue.
Improving error reporting in ZIG so people need to use google search or LLM less is not unreasonable ask in my opinion.
Here is my full comment that likely got me banned. Unwarranted in my opinion
I was looking for issue where to mention my problem as a zig noob.
My first attempt of trying to print value from function that returns union with result+error, I got a verbose generic message, I had to google to make sense of.
invalid format string ‘d’ for type ‘@typeInfo(@typeInfo(@TypeOf(simd.findFromEnd.nthLineOffset)).@“fn”.return_type.?).error_union.error_set!u64’
would be nicer to maybe word it:
invalid format string ‘d’ for error union type ‘anyerror!u64’
seems like this issue is in this direction.
printing an error union could be a very common mistake, so I guess it would not take too long to get used to it, but a hint would be helpful for noobs like me if not too difficult to implement:
hint: did you forget to unwrap the error using ‘try’ or ‘catch’?
I hate it when I have to reach for AI unnecessarily, but regular search on duckduckgo got me confused, the AI hit there was verbose and not very helpful. When asking google gemini I got a really nice concise explanation. I would much rather that we make effort so there is less need to burn forests for thing we notice AI gives better nicer response if it can be short circuited and error message is readable and gives better chance even noob could understand.
Learning zig means I will stumble upon many errors and I would love If I could learn more from the errors before reaching for AI.
No LLMs for brainstorming and then sharing the results of that brainstorming, even if you create the prose. If you use a chatbot to give you advice on a comment on the issue tracker, that comment is unwelcome.
No talking about use of chatbot/LLM services.
Now, you can disagree with said Code of Conduct, but given that you broke the stated rules, I don’t think the response was unreasonable. I know that Zig’s stance on ai is controversial but I don’t think complaining here about its enforcement is constructive.
@videbar thanks for the explanation, I forgot it was that strict. I should have re-read the code of conduct after the ban. Is is fair that ban stays. There is no way in hell I will not consult LLM regarding ZIG code.
I am petty by nature, and I am clearly not compatible, and have no plans of changing to fit here.
I will cancel my small donation to and any attempt to contribute back. I may revisit this in a Year, and maybe it becomes clear that is was good choice to be this strict on LLM.
This one is on me, I should have re-read the code of conduct before commenting on the mentioned codeberg issue, but that is water under the bridge now.