Go to file Use this template
Matej Janezic 000003402f
fix: .cargo/config solve flag order
2023-11-20 21:14:52 +01:00
.cargo fix: .cargo/config solve flag order 2023-11-20 21:14:52 +01:00
.github/workflows feat: fmt ci 2022-12-08 21:29:50 +01:00
src fix: create src/bin/.keep so solver files can be generated 2023-11-20 21:00:16 +01:00
utils feat!: decouple download and scaffold from main package into workspace 2023-11-20 15:44:14 +01:00
.env.example feat: download cli command 2022-11-28 21:59:26 +01:00
.gitignore feat: add github ci for tests, cargo check and clippy 2022-11-30 21:43:29 +01:00
Cargo.lock fix: .cargo/config solve flag order 2023-11-20 21:14:52 +01:00
Cargo.toml fix: .cargo/config solve flag order 2023-11-20 21:14:52 +01:00
LICENSE feat: add MIT license 2022-12-12 22:39:45 +01:00
README.md fix: update README with correct workspace build 2023-11-20 21:03:31 +01:00

README.md

ci

Advent-of-Code {YEAR}

This is a dumbed down version of fspoettel/advent-of-code-rust with some extra features

Project overview

Project structure

  • src/ :
    • bin/:
      • <day>.rs: solution files
    • inputs/: this directory is gitignored, input files go here
    • examples/: example files go here; you can push this as test are run in ci
    • utils/: utils files go here
    • lib.rs: contains framework code
  • .env.example: example dotenv file
  • utils/: binary packages with convenience scripts structured using cargo workspaces

Cli

  • cargo scaffold <day>: prepare solution files for day
  • cargo download <day>: download input file for day
  • cargo solve <day>: run solution against input for day

Run cargo build --workspace --release once so scaffold and download packages get compiled, otherwise they will have to be compiled on first run.

dotenv

set YEAR to whichever year you are solving for and TOKEN to AoC session Cookie

FAQ

How are your commits numbered in ascending order?

https://westling.dev/b/extremely-linear-git