Manlio Perillo

> > but the CI workflow runs correctly > > These messages are from the CI: "Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16:...

@ratfactor Recently I was thinking of writing a `ziglings.zig` program for fun. I'm also interested in how the patch files are created. Should `ziglings` follow the same UI as https://github.com/rust-lang/rustlings?

One problem is how avoid confusing the users if there are both the `build.zig` and `ziglings.zig` files.

@ratfactor ## build.zig vs ziglings.zig My initial concern is what to do with the current `build.zig`. Should we remove it, or should we keep it in is some directory? As...

I forgot about patches. @ratfactor wrote that he wold like to remove the use of `diff` and `patch` and I agree, since it will make it possible to use Windows...

I have implemented a first draft for caching support in `ZiglingStep`. The output is: ``` _ _ _ ___(_) __ _| (_)_ __ __ _ ___ |_ | |/ _'...

Here is the output when nothing is written for cached exercises: ``` _ _ _ ___(_) __ _| (_)_ __ __ _ ___ |_ | |/ _' | | |...

NOTE: the video is marked as corrupted by Firefox. https://github.com/ratfactor/ziglings/assets/6217088/1d2d83a3-22f1-4adf-ac8e-e3a0ec0d54f4

@chrboesch I fixed the problem with skipped exercises. As for showing only recently solved exercises, I think it is very hard, since `ZiglingStep` is pratically stateless. What I tried is...

> The async exercises have currently been removed from the build due to changes in the Zig compiler. This threw me for a loop at first until I looked at...