||1 day ago|
|.github/workflows||1 week ago|
|exercises||1 week ago|
|patches||2 weeks ago|
|.gitattributes||2 years ago|
|.gitignore||2 years ago|
|CONTRIBUTING.md||3 months ago|
|LICENSE||2 years ago|
|README.md||1 day ago|
|build.zig||1 day ago|
Welcome to Ziglings! This project contains a series of tiny broken programs. By fixing them, you'll learn how to read and write Zig code.
Those tiny broken programs need your help! (You'll also save the planet from evil aliens and help some friendly elephants stick together, which is very sweet of you.)
This will probably be difficult if you've never programmed before. But no specific programming experience is required. And in particular, you are not expected to have any prior experience with "systems programming" or a "systems" level language such as C.
Each exercise is self-contained and self-explained. However, you're encouraged to also check out these Zig language resources for more detail:
Also, the Zig community is incredibly friendly and helpful!
Install a development build of the Zig compiler. (See the "master" section of the downloads page.)
Verify the installation and build number of
zig like so:
$ zig version 0.11.0-dev.1568+xxxxxxxxx
Clone this repository with Git:
$ git clone https://github.com/ratfactor/ziglings $ cd ziglings
zig build and follow the instructions to begin!
$ zig build
A Note About Versions
The Zig language is under very active development. In order to be current,
Ziglings tracks development builds of the Zig compiler rather than
versioned release builds. The last stable release was
0.10.1, but Ziglings
needs a dev build with pre-release version "0.11.0" and a build number at least
as high as that shown in the example version check above.
It is likely that you'll download a build which is greater than the minimum.
(For those who cannot easily update Zig, there are also community-supported branches in this repo. At the moment, there's one for v0.8.1. Older version branches may or may not have all exercises and/or bugfixes.)
Once you have a build of the Zig compiler that works with Ziglings, they'll continue to work together. But keep in mind that if you update one, you may need to also update the other.
Also note that the current "stage 1" Zig compiler is very strict about input: no tab characters or Windows CR/LF newlines are allowed.
- 2023-02-04 zig 0.11.0-dev.1568 - changes in
- 2023-01-14 zig 0.11.0-dev.1302 - changes in
@addWithOverflow(now returns a tuple) and
@typeInfo; temporary disabled async functionality
- 2022-09-09 zig 0.10.0-dev.3978 - change in
- 2022-09-06 zig 0.10.0-dev.3880 - Ex 074 correctly fails again: comptime array len
- 2022-08-29 zig 0.10.0-dev.3685 -
@typeName()output change, stage1 req. for async
- 2022-07-31 zig 0.10.0-dev.3385 - std lib string
- 2022-03-19 zig 0.10.0-dev.1427 - method for getting sentinel of type changed
- 2021-12-20 zig 0.9.0-dev.2025 -
- 2021-06-14 zig 0.9.0-dev.137 - std.build.Id
- 2021-04-21 zig 0.8.0-dev.1983 - std.fmt.format()
anyformat string required
- 2021-02-12 zig 0.8.0-dev.1065 - std.fmt.format()
s(string) format string required
It can be handy to check just a single exercise or start from a single exercise:
zig build 19 zig build 19_start
You can also run without checking for correctness:
zig build 19_test
Or skip the build system entirely and interact directly with the compiler if you're into that sort of thing:
zig run exercises/001_hello.zig
Calling all wizards: To prepare an executable for debugging, install it to zig-cache/bin with:
zig build 19_install
I've decide to limit Ziglings to the core language and not attempt coverage of the Standard Library. Perhaps you can change my mind?
- Hello world (main needs to be public)
- Importing standard library
- Errors (error/try/catch/if-else-err)
- Defer (and errdefer)
- Struct methods
- Many-item pointers
- Numeric types (integers, floats)
- Labelled blocks and loops
- Loops as expressions
- Inline loops
- Sentinel termination
- Quoted identifiers @""
- Anonymous structs/tuples/lists
- Async <--- IN PROGRESS!
- Interfaces <--- IN PROGRESS!
- Working with C
Contributions are very welcome! I'm writing this to teach myself and to create the learning resource I wished for. There will be tons of room for improvement:
- Wording of explanations
- Idiomatic usage of Zig
- Maybe additional exercises?
Please see CONTRIBUTING.md in this repo for the full details.