-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Showing
8 changed files
with
339 additions
and
104 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
# TODO make solutions public! | ||
************************************************************ | ||
# Advent of Code 2022 Solutions | ||
Advent of Code [2022](https://adventofcode.com/2022) | ||
|
||
Each year I try to complete the latest [advent calendar](https://adventofcode.com/2022/about) using a languge that is new to me, or that I want more practice in. | ||
|
||
This year I used Clojure. | ||
|
||
## Soutions | ||
The solutions for each day are located in the corresponding .py file i.e. Dec 1st -> day_one.py. | ||
One :star: indicates Part 1 is completed, 2 :star:'s indicate Parts 1 and 2 are completed. | ||
|
||
| Day | Stars| Inputs | Solution | | ||
| ----- | ----- | -------- | ------ | | ||
| 1 | :star::star: | [inputs/day_one.txt](TODO) | [day_one.clj](TODO) | | ||
| 2 | :star: | [inputs/day_two.txt](TODO) | [day_two.clj](TODO) | | ||
| 3 | | TODO | TODO | | ||
| 4 | | TODO | TODO | | ||
| 5 | | TODO | TODO | | ||
| 6 | | TODO | TODO | | ||
| 7 | | TODO | TODO | | ||
| 8 | | TODO | TODO | | ||
| 9 | | TODO | TODO | | ||
| 10 | | TODO | TODO | | ||
| 11 | | TODO | TODO | | ||
| 12 | | TODO | TODO | | ||
| 13 | | TODO | TODO | | ||
| 14 | | TODO | TODO | | ||
| 15 | | TODO | TODO | | ||
| 16 | | TODO | TODO | | ||
| 17 | | TODO | TODO | | ||
| 18 | | TODO | TODO | | ||
| 19 | | TODO | TODO | | ||
| 20 | | TODO | TODO | | ||
| 21 | | TODO | TODO | | ||
| 22 | | TODO | TODO | | ||
| 23 | | TODO | TODO | | ||
| 24 | | TODO | TODO | | ||
| 25 | | TODO | TODO | | ||
|
||
## Execution | ||
Build container | ||
``` | ||
make docker-build | ||
``` | ||
Execute solution | ||
``` | ||
make solve day=<[one,two,twentyfive,etc]> | ||
``` | ||
|
||
## Requirements | ||
- [GNU Make](https://www.gnu.org/software/make/manual/make.html#Simple-Makefile) | ||
- Docker and its runtime env like Docker Desktop or [Colima](https://github.com/abiosoft/colima?tab=readme-ov-file#getting-started) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
# TODO make solutions public! | ||
************************************************************ | ||
# Advent of Code 2023 Solutions | ||
Advent of Code [2023](https://adventofcode.com/2023) | ||
|
||
Each year I try to complete the latest [advent calendar](https://adventofcode.com/2023/about) using a languge that is new to me, or that I want more practice in. | ||
|
||
This year I used Go. | ||
|
||
## Soutions | ||
The solutions for each day are located in the corresponding .py file i.e. Dec 1st -> day_one.py. | ||
One :star: indicates Part 1 is completed, 2 :star:'s indicate Parts 1 and 2 are completed. | ||
|
||
| Day | Stars| Inputs | Solution | | ||
| ----- | ----- | -------- | ------ | | ||
| 1 | :star::star: | [inputs/day_one.txt](TODO) | [day_one.go](TODO) | | ||
| 2 | :star: | [inputs/day_two.txt](TODO) | [day_two.go](TODO) | | ||
| 3 | | TODO | TODO | | ||
| 4 | | TODO | TODO | | ||
| 5 | | TODO | TODO | | ||
| 6 | | TODO | TODO | | ||
| 7 | | TODO | TODO | | ||
| 8 | | TODO | TODO | | ||
| 9 | | TODO | TODO | | ||
| 10 | | TODO | TODO | | ||
| 11 | | TODO | TODO | | ||
| 12 | | TODO | TODO | | ||
| 13 | | TODO | TODO | | ||
| 14 | | TODO | TODO | | ||
| 15 | | TODO | TODO | | ||
| 16 | | TODO | TODO | | ||
| 17 | | TODO | TODO | | ||
| 18 | | TODO | TODO | | ||
| 19 | | TODO | TODO | | ||
| 20 | | TODO | TODO | | ||
| 21 | | TODO | TODO | | ||
| 22 | | TODO | TODO | | ||
| 23 | | TODO | TODO | | ||
| 24 | | TODO | TODO | | ||
| 25 | | TODO | TODO | | ||
|
||
## Execution | ||
Build container | ||
``` | ||
make docker-build | ||
``` | ||
Execute solution | ||
``` | ||
make solve day=<[one,two,twentyfive,etc]> | ||
``` | ||
|
||
## Requirements | ||
- [GNU Make](https://www.gnu.org/software/make/manual/make.html#Simple-Makefile) | ||
- Docker and its runtime env like Docker Desktop or [Colima](https://github.com/abiosoft/colima?tab=readme-ov-file#getting-started) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters