Contact
Rajesh Pillai writes and maintains this guide. Corrections, questions and requests all go to the same place, and he reads all of them.
To contact him directly, send an email to pillai.rajesh@gmail.com. The sections below tell you which channel gives the fastest fix for each type of problem.
Something on a page is wrong
This report is the most useful thing that you can send. Open an issue on the issue tracker. If a report has these four items, the author can usually act on it immediately:
- The URL of the chapter.
- Your Zig version, from
zig version. The guide targets master, and CI last verified it against 0.18.0-dev.828+9da287565. In about half of the reports, a tagged release runs code that was written for master. The chapter Migrate from an Older Zig is about that problem. - The result that you expected.
- The result that you got, with the full error message.
If a snippet does not compile for you on current master, the nightly build will soon fail on it. Please report it immediately. CI compiles and runs every snippet each night, so this problem should not be possible. If it occurs, then the check also has a problem. To learn how the check works, read how this guide is verified.
A chapter is missing, or one is unclear
Use the issue tracker for this too. Say what you tried to do, and where you could not continue. "I could not find how to do X" is more useful than a proposed table of contents. The real gap is usually not where it seems to be.
A correction that you wrote
You can send pull requests to github.com/rajeshpillai/zig-guide. Every snippet is a real file that the build compiles and runs. Thus, when you push a change to example code, CI checks it automatically. The notes in the repository tell how the build classifies snippets, and what a new snippet needs.
Anything else
For a message that does not belong in a public issue, write to pillai.rajesh@gmail.com. Rajesh is also on X as @rajeshpillai.
What this site cannot do
This site has no accounts, no comment system and no server. Nothing here can receive a form or store a message. Thus every route above goes to a different domain. The address at the top goes to a mailbox, not to a program on this site. For the same reason, the privacy page is short.