2021-02-27 19:51:15 +00:00
|
|
|
# Ziglings
|
2020-12-23 17:02:35 +00:00
|
|
|
|
2023-03-12 12:47:13 +00:00
|
|
|
Welcome to Ziglings! This project contains a series of tiny broken programs (and one nasty surprise).
|
2023-03-12 12:47:48 +00:00
|
|
|
By fixing them, you'll learn how to read and write [Zig](https://ziglang.org/) code.
|
2021-02-16 01:04:18 +00:00
|
|
|
|
2021-02-27 19:51:15 +00:00
|
|
|
![ziglings](https://user-images.githubusercontent.com/1458409/109398392-c1069500-790a-11eb-8ed4-7d7d74d32666.jpg)
|
|
|
|
|
2023-03-12 12:49:26 +00:00
|
|
|
Those broken programs need your help! (You'll also save the planet from
|
2021-02-27 19:51:15 +00:00
|
|
|
evil aliens and help some friendly elephants stick together, which is very
|
|
|
|
sweet of you.)
|
2020-12-23 17:02:35 +00:00
|
|
|
|
|
|
|
This project was directly inspired by the brilliant and fun
|
|
|
|
[rustlings](https://github.com/rust-lang/rustlings)
|
|
|
|
project for the [Rust](https://www.rust-lang.org/) language.
|
2021-03-10 19:47:23 +00:00
|
|
|
Indirect inspiration comes from [Ruby Koans](http://rubykoans.com/)
|
2021-02-13 20:47:00 +00:00
|
|
|
and the Little LISPer/Little Schemer series of books.
|
2020-12-23 17:02:35 +00:00
|
|
|
|
2021-02-06 14:29:49 +00:00
|
|
|
## Intended Audience
|
|
|
|
|
2021-02-06 20:54:56 +00:00
|
|
|
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.
|
2021-02-06 14:29:49 +00:00
|
|
|
|
|
|
|
Each exercise is self-contained and self-explained. However, you're encouraged
|
|
|
|
to also check out these Zig language resources for more detail:
|
|
|
|
|
2023-02-19 16:52:16 +00:00
|
|
|
* https://ziglang.org/learn/
|
2021-02-06 14:29:49 +00:00
|
|
|
* https://ziglearn.org/
|
|
|
|
* https://ziglang.org/documentation/master/
|
|
|
|
|
2021-03-10 19:47:23 +00:00
|
|
|
Also, the [Zig community](https://github.com/ziglang/zig/wiki/Community) is incredibly friendly and helpful!
|
|
|
|
|
2020-12-23 17:02:35 +00:00
|
|
|
## Getting Started
|
|
|
|
|
2021-02-16 01:04:18 +00:00
|
|
|
Install a [development build](https://ziglang.org/download/) of the Zig compiler.
|
|
|
|
(See the "master" section of the downloads page.)
|
2020-12-23 17:02:35 +00:00
|
|
|
|
2021-02-16 01:13:50 +00:00
|
|
|
Verify the installation and build number of `zig` like so:
|
2020-12-23 17:02:35 +00:00
|
|
|
|
|
|
|
```bash
|
|
|
|
$ zig version
|
2023-04-07 17:28:33 +01:00
|
|
|
0.11.0-dev.2401+xxxxxxxxx
|
2020-12-23 17:02:35 +00:00
|
|
|
```
|
|
|
|
|
|
|
|
Clone this repository with Git:
|
|
|
|
|
|
|
|
```bash
|
2021-02-14 21:42:42 +00:00
|
|
|
$ git clone https://github.com/ratfactor/ziglings
|
|
|
|
$ cd ziglings
|
2020-12-23 17:02:35 +00:00
|
|
|
```
|
|
|
|
|
build: restore the exercise chain
The new parallel build support in Zig broke the exercise chain, so that
each esercise check is no longer strictly serialized.
1. Add the Dexno option, in order to isolate the chain starting from a
named exercise from the normal chain, thus simplify the code.
The current code have an additional issue: it added 4 x n steps,
making reading the help message or the list of steps very hard.
Add only the `install`, `uninstall`, `zigling`, `test` and `start`
steps. The last three steps match the old steps `n`, `n_test` and
`n_start`.
The default step is zigling (note the singular form).
The `install` step override the builtin install step, showing a
custom description and matches the old `n_install` step.
The uninstall step was added for consistency, so that the
description is consistent.
Setup a new chain starting at `zig build -Dexno=n start` so that it
is stricly serialized.
The behavior should be the same as the old one.
2. Handle the code for all the exercises separately.
Add only the `ziglings step`, making it the default step, in
addition to the install and uninstall steps.
Setup a new chain starting at the first exercise, to that it is
strictly serialized.
The behavior should be the same as the old one.
The current code has a know issue: the messages from the ZiglingStep and
the ones from the compiler compilation progress are interleaved, but each
message is written atomically, due to the use of `std.debug.getStderrMutex()`.
Update the README.md file.
Closes #202
2023-04-06 11:47:08 +01:00
|
|
|
Then run `zig build` and follow the instructions to begin!
|
2020-12-23 17:02:35 +00:00
|
|
|
|
|
|
|
```bash
|
build: restore the exercise chain
The new parallel build support in Zig broke the exercise chain, so that
each esercise check is no longer strictly serialized.
1. Add the Dexno option, in order to isolate the chain starting from a
named exercise from the normal chain, thus simplify the code.
The current code have an additional issue: it added 4 x n steps,
making reading the help message or the list of steps very hard.
Add only the `install`, `uninstall`, `zigling`, `test` and `start`
steps. The last three steps match the old steps `n`, `n_test` and
`n_start`.
The default step is zigling (note the singular form).
The `install` step override the builtin install step, showing a
custom description and matches the old `n_install` step.
The uninstall step was added for consistency, so that the
description is consistent.
Setup a new chain starting at `zig build -Dexno=n start` so that it
is stricly serialized.
The behavior should be the same as the old one.
2. Handle the code for all the exercises separately.
Add only the `ziglings step`, making it the default step, in
addition to the install and uninstall steps.
Setup a new chain starting at the first exercise, to that it is
strictly serialized.
The behavior should be the same as the old one.
The current code has a know issue: the messages from the ZiglingStep and
the ones from the compiler compilation progress are interleaved, but each
message is written atomically, due to the use of `std.debug.getStderrMutex()`.
Update the README.md file.
Closes #202
2023-04-06 11:47:08 +01:00
|
|
|
$ zig build
|
2020-12-23 17:02:35 +00:00
|
|
|
```
|
|
|
|
|
2021-02-14 21:42:42 +00:00
|
|
|
## A Note About Versions
|
2021-02-13 03:53:07 +00:00
|
|
|
|
2021-02-16 01:04:18 +00:00
|
|
|
The Zig language is under very active development. In order to be current,
|
2021-02-16 01:13:50 +00:00
|
|
|
Ziglings tracks **development** builds of the Zig compiler rather than
|
2023-01-31 23:04:50 +00:00
|
|
|
versioned **release** builds. The last stable release was `0.10.1`, but Ziglings
|
2023-01-14 11:56:52 +00:00
|
|
|
needs a dev build with pre-release version "0.11.0" and a build number at least
|
2021-02-16 01:13:50 +00:00
|
|
|
as high as that shown in the example version check above.
|
2021-02-15 00:25:35 +00:00
|
|
|
|
|
|
|
It is likely that you'll download a build which is _greater_ than the minimum.
|
2021-02-13 03:53:07 +00:00
|
|
|
|
2021-12-20 19:49:25 +00:00
|
|
|
_(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.)_
|
|
|
|
|
2021-02-16 01:04:18 +00:00
|
|
|
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
|
2021-02-15 00:25:35 +00:00
|
|
|
need to also update the other.
|
2021-02-13 03:53:07 +00:00
|
|
|
|
2021-06-30 22:30:01 +01:00
|
|
|
Also note that the current "stage 1" Zig compiler is very strict
|
|
|
|
about input:
|
2021-06-30 22:33:38 +01:00
|
|
|
[no tab characters or Windows CR/LF newlines are allowed](https://github.com/ziglang/zig/issues/544).
|
2021-06-30 22:30:01 +01:00
|
|
|
|
2021-04-21 14:47:16 +01:00
|
|
|
### Version Changes
|
2022-03-19 23:42:22 +00:00
|
|
|
|
2023-04-07 17:28:33 +01:00
|
|
|
Version-0.11.0-dev.2401+xxxxxxxxx
|
2023-03-19 17:23:35 +00:00
|
|
|
* *2023-02-21* zig 0.11.0-dev.2157 - changes in `build system` - new: parallel processing of the build steps
|
2023-02-22 10:22:41 +00:00
|
|
|
* *2023-02-21* zig 0.11.0-dev.1711 - changes in `for loops` - new: Multi-Object For-Loops + Struct-of-Arrays
|
2023-02-15 18:28:27 +00:00
|
|
|
* *2023-02-12* zig 0.11.0-dev.1638 - changes in `std.Build` cache_root now returns a directory struct
|
2023-02-04 14:20:54 +00:00
|
|
|
* *2023-02-04* zig 0.11.0-dev.1568 - changes in `std.Build` (combine `std.build` and `std.build.Builder` into `std.Build`)
|
2023-01-21 13:19:48 +00:00
|
|
|
* *2023-01-14* zig 0.11.0-dev.1302 - changes in `@addWithOverflow` (now returns a tuple) and `@typeInfo`; temporary disabled async functionality
|
2022-09-10 19:41:40 +01:00
|
|
|
* *2022-09-09* zig 0.10.0-dev.3978 - change in `NativeTargetInfo.detect` in build
|
2022-09-06 13:28:31 +01:00
|
|
|
* *2022-09-06* zig 0.10.0-dev.3880 - Ex 074 correctly fails again: comptime array len
|
2022-09-10 19:41:40 +01:00
|
|
|
* *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 `fmt()` option changes
|
2022-03-19 23:42:22 +00:00
|
|
|
* *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 - `c_void` is now `anyopaque`
|
|
|
|
* *2021-06-14* zig 0.9.0-dev.137 - std.build.Id `.Custom` is now `.custom`
|
|
|
|
* *2021-04-21* zig 0.8.0-dev.1983 - std.fmt.format() `any` format string required
|
|
|
|
* *2021-02-12* zig 0.8.0-dev.1065 - std.fmt.format() `s` (string) format string required
|
2021-04-21 14:47:16 +01:00
|
|
|
|
2021-02-14 21:42:42 +00:00
|
|
|
## Advanced Usage
|
2020-12-23 17:02:35 +00:00
|
|
|
|
2021-02-14 21:42:42 +00:00
|
|
|
It can be handy to check just a single exercise or _start_ from a single
|
|
|
|
exercise:
|
2020-12-23 17:02:35 +00:00
|
|
|
|
|
|
|
```bash
|
2021-02-14 21:42:42 +00:00
|
|
|
zig build 19
|
|
|
|
zig build 19_start
|
2020-12-23 17:02:35 +00:00
|
|
|
```
|
2021-02-14 21:42:42 +00:00
|
|
|
|
|
|
|
You can also run without checking for correctness:
|
|
|
|
|
2021-02-12 04:04:36 +00:00
|
|
|
```bash
|
2021-03-13 00:09:35 +00:00
|
|
|
zig build 19_test
|
2021-02-12 04:04:36 +00:00
|
|
|
```
|
|
|
|
|
2021-02-14 21:42:42 +00:00
|
|
|
Or skip the build system entirely and interact directly with the compiler
|
|
|
|
if you're into that sort of thing:
|
2021-02-12 04:04:36 +00:00
|
|
|
|
|
|
|
```bash
|
2021-03-13 00:09:35 +00:00
|
|
|
zig run exercises/001_hello.zig
|
2021-02-12 04:04:36 +00:00
|
|
|
```
|
|
|
|
|
2021-02-14 21:42:42 +00:00
|
|
|
Calling all wizards: To prepare an executable for debugging, install it
|
|
|
|
to zig-cache/bin with:
|
2021-02-12 04:04:36 +00:00
|
|
|
|
|
|
|
```bash
|
2021-03-13 00:09:35 +00:00
|
|
|
zig build 19_install
|
2021-02-12 04:04:36 +00:00
|
|
|
```
|
2020-12-23 17:02:35 +00:00
|
|
|
|
2021-11-08 01:52:05 +00:00
|
|
|
## What's Covered
|
2020-12-23 17:02:35 +00:00
|
|
|
|
2021-11-08 01:52:05 +00:00
|
|
|
I've decide to limit Ziglings to the core language and not
|
|
|
|
attempt coverage of the Standard Library. Perhaps you can change
|
|
|
|
my mind?
|
2020-12-23 17:02:35 +00:00
|
|
|
|
2021-05-01 02:35:56 +01:00
|
|
|
Core Language
|
|
|
|
|
2021-01-03 17:21:11 +00:00
|
|
|
* [x] Hello world (main needs to be public)
|
|
|
|
* [x] Importing standard library
|
2021-01-03 23:55:45 +00:00
|
|
|
* [x] Assignment
|
2021-01-04 01:34:26 +00:00
|
|
|
* [x] Arrays
|
2021-01-06 00:26:02 +00:00
|
|
|
* [x] Strings
|
2021-01-08 22:53:22 +00:00
|
|
|
* [x] If
|
2021-01-10 16:46:42 +00:00
|
|
|
* [x] While
|
2021-01-19 00:21:18 +00:00
|
|
|
* [x] For
|
2021-01-22 22:42:03 +00:00
|
|
|
* [x] Functions
|
2021-02-04 00:19:31 +00:00
|
|
|
* [x] Errors (error/try/catch/if-else-err)
|
|
|
|
* [x] Defer (and errdefer)
|
2021-01-31 22:48:34 +00:00
|
|
|
* [x] Switch
|
2021-02-04 00:19:31 +00:00
|
|
|
* [x] Unreachable
|
2021-02-06 14:29:49 +00:00
|
|
|
* [x] Enums
|
2021-02-09 01:35:28 +00:00
|
|
|
* [x] Structs
|
|
|
|
* [x] Pointers
|
2021-02-17 01:28:34 +00:00
|
|
|
* [x] Optionals
|
2021-02-28 18:23:22 +00:00
|
|
|
* [x] Struct methods
|
2021-03-07 02:31:55 +00:00
|
|
|
* [x] Slices
|
2021-03-13 21:27:14 +00:00
|
|
|
* [x] Many-item pointers
|
2021-03-10 01:04:43 +00:00
|
|
|
* [x] Unions
|
2021-04-10 16:39:11 +01:00
|
|
|
* [x] Numeric types (integers, floats)
|
|
|
|
* [x] Labelled blocks and loops
|
|
|
|
* [x] Loops as expressions
|
2021-04-11 16:22:38 +01:00
|
|
|
* [x] Builtins
|
2021-05-01 02:35:56 +01:00
|
|
|
* [x] Inline loops
|
|
|
|
* [x] Comptime
|
2021-05-07 01:32:36 +01:00
|
|
|
* [x] Sentinel termination
|
2021-05-09 18:10:09 +01:00
|
|
|
* [x] Quoted identifiers @""
|
2021-05-10 00:53:14 +01:00
|
|
|
* [x] Anonymous structs/tuples/lists
|
2021-11-08 01:52:05 +00:00
|
|
|
* [ ] Async <--- IN PROGRESS!
|
2023-02-16 09:35:15 +00:00
|
|
|
* [X] Interfaces
|
2023-02-16 18:44:35 +00:00
|
|
|
* [X] Working with C
|
2023-02-19 20:59:52 +00:00
|
|
|
* [ ] String formatting
|
2021-11-08 01:52:05 +00:00
|
|
|
|
|
|
|
## Contributing
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|