advent-of-code VS advent-of-code

github (final version) and paste

Took a while to come up with a data structure that would make the moves efficiently. After a bit of thought today I realized I could use a (single) linked list with a dictionary from cup label to list node. Code: github (v1) runs in < 15 seconds on my machine.

My solution in Common Lisp.

Just a simple relief-shaded image like you might find on a map. Principally generated with GDAL. The particular commands used are at the bottom of my solution code for the day. I also made a more flat version, which shows the elevation colors better, but really doesn't feel right in terms of elevation.

So I spend more time analyzing the input calculation. I wrote up that analysis and committed it to my repository, too.

This was a bit difficult. My original part one solution worked completely differently to what I had to do for part two.

My solution in Common Lisp, 2335/2041.

No. It's just here, as part of my Advent of Code repository.

The code is at the bottom of my day 9 source file, in Common Lisp. (The AdvMAME3x code was something I originally wrote for my 2020 day 20 visualization.)

As a side note, I took inspiration from a post the other day about adding AoC badges to your repository README file. I use GitLab, which lets you define badges as properties of your repository. So I added badges to my repository's header area, driven by a JSON file in the repository. The JSON file is updated manually by a script. (I might add some automated updates at some point, but manual works okay for now.)

Probably overkill, because I parsed the instructions into instances of my point class. I tend to default to that for coordinates nowadays (as opposed to just using complex numbers) because it generically extends to arbitrary numbers of dimensions. Just in case.

My solution in Common Lisp.