Awesome
adventofcode
A repository for V language solutions to Advent of Code puzzles.
Initial layout:
A directory for the year, with subdirs for each day.
Inside each day subdir, example input file for that day, and individual solutions named
by the GitHub ID of the person who supplied it followed by .v
to identify it as a V
language file.
If you have a solution that is more complex than a single .v
file, make a subdir with
your GitHub ID under the appropriate year/day subdir, and place all files there.
Input file format
- Input file should end with file extension
.input
- Input file should be directly copied/pasted from AoC's example input with the following
standard:
- No whitespace trimming (see Note 1 below)
- No additional empty line
- No personal-specific input allowed in example input file
- If there are multiple example inputs for different parts in a day, suffix each
input file with
-partX
where X is part number, then follow other criteria - Input file's name should relate to the corresponding AoC problem, for example: AoC 2022
Day 7 relates to unix system's file system cmd operations, therefore, you should
name it
filesystem.input
orcmd.input
Note 1: when you add .input
files, please turn off the auto trimming
functionality of your editor/IDE. Some solutions require the .input
files to have the exact same format that AoC uses, and trimming end
lines may break them.
Note 2: there is a small script that can be used to verify that all
solutions continue to work with latest V versions. You can use it by
running v run verify.v
in the top folder of this repository.
It will produce the necessary .out
files for new solutions, and you
can commit them so that the CI will check that there are no
regressions.
Leaderboard
Feel free to join the vlang leaderboard: 1303110-4f92d16a
.