Check out the new version of AOC-Helper which is now a library and much easier to setup: https://github.com/jjcomer/aoc-clj-elf
Clojure based AOC helper.
This is a set of scripts which will help you work on Advent Of Code puzzles.
Specifically it will help you:
- Pull puzzle input from AOC (and store to disk)
- Generate solution files
- Execute tests within your solutions
- Run your solutions with the pulled input (and time your execution)
This framework also supports having multiple years together in the same repository. Your session for each year is different so you will need to add an auth for each year you want to use.
Before you use this framework there is a pre-requisite of babashka
On a mac you can install babashka using brew:
$ brew install babashka
For other installation instructions see the official docs
This repository is already setup for you to start coding. You can clone directly and then delete the .git
folder and init a new git repo for your own usage.
In order to be able to pull input for your puzzles you will need to provide your AOC session cookie value from your browser.
TODO Instructions for finding cookie value
Once you have your token, you will need to store the value for the scipts to use. This is done using the auth
command:
$ bb auth :year <YEAR> :session <SESSION TOKEN>
If you don't specify a year, the script will assume the current year. You can store session tokens for multiple years within the same repo.
Session tokens are stored within the auth.edn
file at the root of the repo. This file has already been added to the .gitignore
file to prevent accidental check-ins.
When you are ready to start solving a problem the framework can generate a starting file for you to use and which will be compatible with the included runners.
To create a new solution file execute the new
task:
$ bb new :year <YEAR> :day <DAY>
This will create a new file under src/y<YEAR>/d<DAY>.clj
Your puzzle input can be downloaded directly from AOC. Using the get
task you can pull any available input. With no parameters the input for today will be pulled.
$ bb get :year <YEAR> :day <DAY>
If the input has already been pulled, the task will not re-pull the input.
A clojure.test
runner has also been included if you want to write tests against your solution. This can be a helpful way to use the samples which are provided in the puzzles each day.
All tests in the solution's namespace will be executed. To run your tests use the test
task.
$ bb test :year <YEAR> :day <DAY>
When you are ready to run your solution, the framework is ready to help with the run
task. This task will check for input and automatically download if missing. The input will be passed to the generator fn within your ns. The result of the generator will be passed to both the part-1
and part-2
solving functions. The result of both functions will be printed. If no parameters are passed today's date will be used.
$ bb solve :year <YEAR> :day <DAY>
If you solutions need any additional dependencies you can add them to the :deps
map within the bb.edn
. They will be pull automatically on the next task execution.
Currently all solutions will run within GraalVM and more specifically the babashka runtime environment. Not all features of clojure are supported. There are a number of libraries pre-included with babashka that you can make use of with no additional configuration. See the docs for more information.
If you would like to change the templated solution files, the template is found at scripts\solution_template.clj
Allow for using JVM clojure (for more speed)- Support for multiple solutions per-day
- Switch to macros for defining generators
- Switch to macros for defining solvers
- Criterion (Benchmarking) integration
- Ability to run all days sequentially
- Optionally pprint solution output
- More emojis ☃️
- Better output formatting
- Provide a filter for only running particular tests
- Add docs for connecting REPLs
- Add docs on finding session cookie
- Changed all execution to babashka
- Removed benchmarking as it does not work on GraalVM
- Update User-Agent as per request
- Added
bench
task using criterium to benchmark solution time - Added section for generator logic to the solution template
- Changed over to execute using the JVM (will add back BB execution)
- Breaking changed the parameters to keywords and updated documentation
- Added
.tools-version
file to help choose a compatible jvm