Go to file Use this template
Matej Janezic 0000044040
fix: .env.example and filetree in README
2023-11-28 00:54:12 +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
data feat: move data files out of src/ 2023-11-23 00:01:54 +01:00
src feat: trim solution macro 2023-11-27 21:34:27 +01:00
utils feat: move template code into its own module 2023-11-23 23:59:03 +01:00
.env.example fix: .env.example and filetree in README 2023-11-28 00:54:12 +01:00
.gitignore feat: move data files out of src/ 2023-11-23 00:01:54 +01:00
Cargo.lock fix: .env.example and filetree in README 2023-11-28 00:54:12 +01:00
Cargo.toml fix: .env.example and filetree in README 2023-11-28 00:54:12 +01:00
LICENSE feat: update LICENSE year 2023-11-22 11:30:04 +01:00
README.md fix: .env.example and filetree in README 2023-11-28 00:54:12 +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

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

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