Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/wieerwill/advent_of_code_2023
my solutions for the advent of code 2023 in Rust, Python, JS and TS
https://github.com/wieerwill/advent_of_code_2023
advent-of-code advent-of-code-2023 javascript python rust typescript
Last synced: 6 days ago
JSON representation
my solutions for the advent of code 2023 in Rust, Python, JS and TS
- Host: GitHub
- URL: https://github.com/wieerwill/advent_of_code_2023
- Owner: wieerwill
- License: gpl-3.0
- Created: 2023-12-01T16:48:06.000Z (12 months ago)
- Default Branch: main
- Last Pushed: 2023-12-23T12:57:55.000Z (11 months ago)
- Last Synced: 2023-12-23T15:32:03.903Z (11 months ago)
- Topics: advent-of-code, advent-of-code-2023, javascript, python, rust, typescript
- Language: Python
- Homepage: https://adventofcode.com/
- Size: 2.54 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# 🎄 Advent of Code 2023 🎄
Welcome to my repository where I share my solutions for the [Advent of Code 2023](https://adventofcode.com/2023). Advent of Code is an annual online event where participants solve a series of programming puzzles released daily from December 1st until December 25th. Each puzzle is a fun and unique challenge designed to test problem-solving skills.
## Structure
This repository is organized to make navigation through the solutions as seamless as possible.
Each day's puzzle solution is in its respective folder, named `DayXX`, where `XX` is the day of the month.
- `Day01`
- `Day02`
- `...`
- `Day25`
Within each folder, you'll find:
- `README.md`: A brief description of the day's problem.
- Source code files: My solution for the day's puzzle, typically in Python or Rust
- `input.txt`: The input data provided for the puzzle. (add those yourself as we don't provide those for legal reasons)
- Additional resources or notes if applicable.
## My Approach
For Advent of Code 2023, I've decided to primarily use Python due to its readability and the extensive libraries available, which make it an excellent choice for solving diverse and complex problems quickly. In each solution, I focus not only on solving the problem but also on writing clean, efficient, and well-documented code.
## 📈 Progress
Here I'll track my progress throughout the event.
I aim to complete each day's puzzle on the same day, but as with any challenge, there might be some delays.
| Day | Part One | Part Two | Reflections |
|-----|----------|----------|-------------|
| 01 | ✅ | ✅ | [Day01 README](/Day01/README.md) |
| 02 | ✅ | ✅ | [Day02 README](/Day02/README.md) |
| 03 | ✅ | ✅ | [Day03 README](/Day03/README.md) |
| 04 | ✅ | ✅ | [Day04 README](/Day04/README.md) |
| 05 | ✅ | ✅ | [Day05 README](/Day05/README.md) |
| 06 | ✅ | ✅ | [Day06 README](/Day06/README.md) |
| 07 | ✅ | ✅ | [Day07 README](/Day07/README.md) |
| 08 | ✅ | ✅ | [Day08 README](/Day08/README.md) |
| 09 | ✅ | ✅ | [Day09 README](/Day09/README.md) |
| 10 | ✅ | ✅ | [Day10 README](/Day10/README.md) |
| 11 | ✅ | ✅ | [Day11 README](/Day11/README.md) |
| 12 | ✅ | ✅ | [Day12 README](/Day12/README.md) |
| 13 | ✅ | ✅ | [Day13 README](/Day13/README.md) |
| 14 | ✅ | ❓ | [Day14 README](/Day14/README.md) |
| 15 | ✅ | ✅ | [Day15 README](/Day15/README.md) |
| 16 | ✅ | ✅ | [Day16 README](/Day16/README.md) |
| 17 | ✅ | ✅ | [Day17 README](/Day17/README.md) |
| 18 | ✅ | ✅ | [Day18 README](/Day18/README.md) |
| 19 | ✅ | ✅ | [Day19 README](/Day19/README.md) |
| 20 | ❓ | ❓ | [Day20 README](/Day20/README.md) |
| 21 | ❓ | ❓ | [Day21 README](/Day21/README.md) |
| 22 | ❓ | ❓ | [Day22 README](/Day22/README.md) |
| 23 | ❓ | ❓ | [Day23 README](/Day23/README.md) |
| 24 | ❓ | ❓ | [Day24 README](/Day24/README.md) |
| 25 | ❓ | ❓ | [Day25 README](/Day25/README.md) |
- ✅ Completed
- ❓ Not Started / In Progress
## Running the Solutions
Each solution is a standalone script.
## Python
To run any of the solutions, navigate to the respective day's directory and run the script using a Python interpreter.
For example:
```bash
cd Day01/python
python3 solution2.py
python3 solution2.py
```
Make sure you have Python installed on your machine. The solutions are developed using Python 3.x.
## Rust
For Rust you have to use the rust project generated in each Day.
Make sure you have Rust and Cargo installed.
You can either test or run the solution:
```bash
cd Day01/rust
cargo test #running tests
cargo run # run with the actual input file
```
## C++
Install a C++ compiler like g++ on your machine. Then:
```bash
cd Day01/cpp
g++ -o solution solution.cpp # compile
./solution #run the binary
```
## JavaScript
Using solutions in JavaScript requires NodeJS installed on your system. Then:
```bash
cd Day01/js
node solution.js
```
## TypeScript
Normally you can use compile the TS file to JS using the tsc compiler. But for ease in this simple scripts i suggest installing: `npm install -g typescript ts-node`. With this you can just run the TS file at once and get the output without compiling and running over and over.
```bash
cd Day01/ts
ts-node solution.ts
```
---
The first part (less complex) is only solved in Python. Therefore the python folder has always two scripts (solution1.py and solution2.py) to solve both parts. All other languages are only implementing the second part.
## Feedback and Collaboration
I'm always open to feedback and suggestions for improving the solutions.
If you have ideas or find an issue, feel free to open an issue or submit a pull request.