1
1
# adventofcode
2
2
3
- A repository for solutions to [ Advent of Code] ( https://adventofcode.com/about ) puzzles,
4
- written in the [ V] ( https://vlang.io/ ) language.
3
+ A repository for V language solutions to [ Advent of Code] ( https://adventofcode.com/about ) puzzles.
5
4
6
5
Initial layout:
7
6
@@ -16,26 +15,26 @@ your GitHub ID under the appropriate year/day subdir, and place all files there.
16
15
17
16
## Input file format
18
17
19
- 1 . Input file should end with file extension ` .input `
20
- 2 . Input file should be directly copied/pasted from AoC's example input with the following
18
+ 1 . Input file should end with file extension ` .input `
19
+ 2 . Input file should be directly copied/pasted from AoC's example input with the following
21
20
standard:
22
- - - No whitespace trimming (see note 1 )
23
- - - No additional empty line
24
- - - No personal-specific input allowed in example input file
25
- 3 . If there are multiple example inputs for different parts in a day, suffix different
26
- input file with ` -partX ` where X is part number, then follow other citeria
21
+ - No whitespace trimming (see Note 1 below )
22
+ - No additional empty line
23
+ - No personal-specific input allowed in example input file
24
+ 3 . If there are multiple example inputs for different parts in a day, suffix each
25
+ input file with ` -partX ` where X is part number, then follow other criteria
27
26
4 . Input file's name should relate to the corresponding AoC problem, for example: AoC 2022
28
27
Day 7 relates to unix system's file system cmd operations, therefore, you should
29
- name it with ` filesystem.input ` or ` cmd.input `
28
+ name it ` filesystem.input ` or ` cmd.input `
30
29
31
- Note 1: when you add .input files, please turn off the auto trimming
32
- functionality of your editor/IDE. Some solutions require the .input
30
+ Note 1: when you add ` .input ` files, please turn off the auto trimming
31
+ functionality of your editor/IDE. Some solutions require the ` .input `
33
32
files to have the exact same format that AoC uses, and trimming end
34
33
lines may break them.
35
34
36
35
Note 2: there is a small script that can be used to verify that all
37
36
solutions continue to work with latest V versions. You can use it by
38
37
running ` v run verify.v ` in the top folder of this repository.
39
- It will produce the necessary .out files for new solutions, and you
40
- can just commit them, so that the CI will check that there are no
38
+ It will produce the necessary ` .out ` files for new solutions, and you
39
+ can commit them so that the CI will check that there are no
41
40
regressions.
0 commit comments