Day | Part 1 | Part 2 |
---|---|---|
Day 1 | ⭐ | ⭐ |
Day 2 | ⭐ | ⭐ |
Day 3 | ⭐ | ⭐ |
Day 4 | ⭐ | ⭐ |
Day 5 | ⭐ | ⭐ |
Day 6 | ⭐ | ⭐ |
Day 7 | ⭐ | ⭐ |
Day 8 | ⭐ | ⭐ |
Day 9 | ⭐ | ⭐ |
Day 10 | ⭐ | ⭐ |
Day 11 | ⭐ | ⭐ |
Day 12 | ⭐ | ⭐ |
Day 13 | ⭐ | ⭐ |
Day 14 | ⭐ | ⭐ |
Day 15 | ⭐ | ⭐ |
Day 16 | ⭐ | ⭐ |
Day 17 | ⭐ | ⭐ |
Day 18 | ⭐ | ⭐ |
Day 19 | ⭐ | ⭐ |
Day 20 | ⭐ | ⭐ |
Day 21 | ⭐ | ⭐ |
Day 22 | ⭐ | ⭐ |
Day 23 | ⭐ | ⭐ |
Day 24 | ⭐ | ⭐ |
Day 25 | ⭐ | ⭐ |
Generated with the advent-of-code-rust template.
- Open the advent-of-code-rust template on Github.
- Click
Use this template
and create your repository. - Clone the repository to your machine.
- Install the Rust toolchain.
- (optional) Install rust-analyzer for your editor.
- (optional) Install a native debugger, e.g. CodeLLDB for VS Code.
- (optional) Install
aoc-cli
and follow their setup guide to use thedownload
script for puzzle inputs. (see below) - (optional) Setup the README stars github action. (see below)
# example: `./scripts/scaffold.sh 1`
./scripts/scaffold.sh <day>
# output:
# Created module `src/solutions/day01.rs`
# Created input file `src/inputs/day01.txt`
# Created example file `src/examples/day01.txt`
# Linked new module in `src/main.rs`
# Linked new module in `src/solutions/mod.rs`
# Done! 🎄
Every solution file has unit tests referencing the example input file. You can use these tests to develop and debug your solution. When editing a solution file, rust-analyzer
will display buttons for these actions above the unit tests.
# example: `./scripts/download.sh 1`
./scripts/download.sh <day>
# output:
# Invoking `aoc` cli...
# Loaded session cookie from "/home/foo/.adventofcode.session".
# Downloading input for day 1, 2021...
# Saving puzzle input to "/tmp/..."...
# Done!
# Wrote input to `src/inputs/day01.txt`...
# Done! 🎄
Puzzle inputs are not checked into git. See here why.
# example: `cargo run 1`
cargo run <day>
# output:
# Running `target/debug/aoc 1`
# ----
#
# 🎄 Part 1 🎄
#
# 6 (elapsed: 37.03µs)
#
# 🎄 Part 2 🎄
#
# 9 (elapsed: 33.18µs)
#
# ----
To run an optimized version for benchmarking, use the --release
flag or the alias cargo rr <day>
.
cargo test
cargo fmt
cargo clippy
This template includes a Github action that automatically updates the readme with your advent of code progress.
To enable it, you need to do two things:
- set repository secrets.
- create a private leaderboard.
Go to the Secrets tab in your repository settings and create the following secrets:
AOC_USER_ID
: Go to this page and copy your user id. It's the number behind the#
symbol in the first name option. Example:3031
AOC_YEAR
: the year you want to track. Example:2021
AOC_SESSION
: an active session for the advent of code website. To get this, press F12 anywhere on the Advent of Code website to open your browser developer tools. Look in your Cookies under the Application or Storage tab, and copy out thesession
cookie.
Go to the leaderboard page of the year you want to track and click Private Leaderboard. If you have not created a leaderboard yet, create one by clicking Create It. Your leaderboard should be accessible under https://adventofcode.com/{year}/leaderboard/private/view/{aoc_user_id}
.