This was necessary in the past (commit 30db9d, 2023-04-17).
The new Progress.zig and, probably, the fact that exercises run on a
separate executable solved the problem.
Also, start from 1 in the positive direction, instead of 5, since that
is more how the thing works (sorry, mathematician brain).
Additionally, adds some extra information in the comments:
information about how long the code would take if one actually sets
count to 2,5 * 10^12, and adding a plus in front of the 4/1 to show that
that is in fact the first element of the "plus" side.
Finally, add an (floating point) error to the debug print.
Updated the exercise to use SIMD. This allows us to
cross-reference the concept from 112_vectors back to 005_arrays2,
introducing a handy feature of vectors early on.
See #430
The new API add support for NO_COLOR and CLICOLOR_FORCE.
Move color variables to a namespace.
Add a message in case colors are not available un unix systems.
Add a message in case on Windows colors are available (on old versions).
Parse the command line following the code from the Zig compiler cli.
Use the args iterator instead of slice, and use while instead of for
loop.
Use the new std.mem.cutPrefix instead of the custom function prefix.
Move Context struct to the top.
Manlio Perillo