Louis Vallat
c3d8a17e86
All checks were successful
Build and run challenges / Challenge for day (1) (push) Successful in 15s
Build and run challenges / Challenge for day (10) (push) Successful in 14s
Build and run challenges / Challenge for day (11) (push) Successful in 14s
Build and run challenges / Challenge for day (13) (push) Successful in 20s
Build and run challenges / Challenge for day (15) (push) Successful in 24s
Build and run challenges / Challenge for day (12) (push) Successful in 32s
Build and run challenges / Challenge for day (14) (push) Successful in 28s
Build and run challenges / Challenge for day (16) (push) Successful in 34s
Build and run challenges / Challenge for day (18) (push) Successful in 35s
Build and run challenges / Challenge for day (22) (push) Successful in 30s
Build and run challenges / Challenge for day (19) (push) Successful in 39s
Build and run challenges / Challenge for day (17) (push) Successful in 43s
Build and run challenges / Challenge for day (2) (push) Successful in 38s
Build and run challenges / Challenge for day (23) (push) Successful in 32s
Build and run challenges / Challenge for day (5) (push) Successful in 25s
Build and run challenges / Challenge for day (21) (push) Successful in 43s
Build and run challenges / Challenge for day (20) (push) Successful in 45s
Build and run challenges / Challenge for day (3) (push) Successful in 36s
Build and run challenges / Challenge for day (7) (push) Successful in 29s
Build and run challenges / Challenge for day (24) (push) Successful in 42s
Build and run challenges / Challenge for day (4) (push) Successful in 38s
Build and run challenges / Challenge for day (25) (push) Successful in 42s
Build and run challenges / Challenge for day (6) (push) Successful in 35s
Build and run challenges / Challenge for day (8) (push) Successful in 32s
Build and run challenges / Challenge for day (9) (push) Successful in 29s
Signed-off-by: Louis Vallat <contact@louis-vallat.dev> |
||
|---|---|---|
| .gitea/workflows | ||
| day1 | ||
| day2 | ||
| day3 | ||
| day4 | ||
| day5 | ||
| day6 | ||
| day7 | ||
| day8 | ||
| day9 | ||
| day10 | ||
| day11 | ||
| day12 | ||
| day13 | ||
| day14 | ||
| day15 | ||
| day16 | ||
| day17 | ||
| day18 | ||
| day19 | ||
| day20 | ||
| day21 | ||
| day22 | ||
| day23 | ||
| day24 | ||
| day25 | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| LICENSE | ||
| README.md | ||
Advent Of Code 2021
Find the sleigh key to save Santa, using your smol submarine!
What
This repository hosts the code that I produced to solve the different puzzles provided for the Advent of Code 2021, that you can find here.
How
In order to solve the different puzzles, I used the Rust programming language, as I wanted a way to experiment and practice this new language.
There are no dependencies and no external crate.
To execute it, just open the specific day you want to run, and use cargo run --release -- ./input.
Replacing the input file should work without any code modification.
Why
Because puzzles are fun! And Rust is fun too!
Yikes
The code produced may not be optimal nor the fastest. And that's normal, I tried to spend less than a day (and to do it in my spare time after school).
The code is also very ugly for a reason: usually I use single letters for the variable names. Usually it's fine. For me. For other people re reading me, it's less fun. So I forced myself to use mainly single characters as variable names, just to make me want to stop doing it.