Advent of Code Data

Programmatically get your puzzle input and submit answers, in Rust.

Might be useful for lazy Rustaceans and speed hackers.

Yes, this is wimglenn's aocd Python-package, but for Rust. And yes, this too tries to cache everything it gets from Advent of Code to spare their servers.

Example

Spoiler: This example does in fact solve one of the AoC puzzles.

use aocd::*;
// or, if you prefer: use aocd::prelude::*;

#[aocd(2022, 1)]
fn main() {
    let mut elves: Vec<_> = input!()
        .split("\n\n")
        .map(|e| e.lines().map(|l| l.parse::<u32>().unwrap()).sum())
        .collect();
    elves.sort();

    submit!(1, elves.last().unwrap());
    submit!(2, elves.iter().rev().take(3).sum::<u32>());
}

Testing

If you want to use a smaller test input while debugging, this can be done by just adding the file name at the top. In this case, the input! macro simply reads the file, and submit! just prints the result without submitting to AoC.

use aocd::*;

#[aocd(2022, 1, "test.txt")]
fn main() {
    ...
}

Quickstart

You need to provide your AoC session token in order for this crate to get your personal puzzle input and to be able to submit answers for you. This is a cookie which is set when you login to AoC. You can find it with your browser inspector. See this issue for a how-to. You can provide it to aocd using any of the following alternatives:

# Alt 1 (this way doesn't require any environment variables to be set):
mkdir -p ~/.config/aocd
echo "your session cookie here" > ~/.config/aocd/token

# Alt 2:
export AOC_SESSION="or here"

# Alt 3:
export AOC_TOKEN="or here"

# Alt 4:
echo "or here" > some_file
export AOC_TOKEN_PATH=some_file

Next, add the crate to your dependencies:

cargo add aocd

In your code, annotate your main function with #[aocd(year, day)], and then use the macros input!() and submit!(part, answer) to get your puzzle input and submit answers, respectively. See the example above.