acef5fdc12
Day 5 solution
...
This required an overhaul of the intcode machine to actually be its own type that could operate on its own memory and stuff. So I had to touch day 2 to make it adhere to the new API.
Feeling good about this foundation now. Until I get gobsmacked at some point later, which I expect to happen.
2022-06-13 15:29:18 -05:00
6d3627e93b
Improve output formatting
...
Adds some whitespace, a divider, and indents each part's output a bit.
2022-06-10 10:34:44 -05:00
40d5eb59be
Add flags to only run a specific part
...
Now we can specify to only run part1 or part2 of the given day(s). Just in case we need some super focused testing or debugging!
2022-06-10 09:56:37 -05:00
c9cfffcc1c
Show timing information when running all days
2022-06-10 09:15:08 -05:00
28ea3ff6a1
Handle an empty argument
...
This makes it slightly easier to adjust VSCode's launch.json to hop around debugging different days. Not much, but a little. And every little bit helps!
2022-06-09 13:17:51 -05:00
bc8ebae440
Day 4 solution
...
Plenty of room for optimization here, but it's enough for my needs for now.
2022-06-09 08:23:34 -05:00
a53e3467fe
Make the linter happy
...
I mean, it's right, but still...
2022-06-08 18:03:08 -05:00
8ec5aafcc2
Day 3 solution
...
This is horrendous and slow. But it works. I really don't like grid problems.
2022-06-08 08:23:07 -05:00
092fe15b07
Fix running "all" tests out of order sometimes
...
Maps are unordered, so this uses an array, which is simpler overall, really.
2022-06-07 22:54:11 -05:00
93c9bc7d6f
Day 2 initial solution
...
There's room to optimize part 2, but I wanted to commit my original brute-force solution first.
2022-06-07 09:26:21 -05:00
d2fbe85a71
Set to automatically run the most recent day
2022-06-07 09:14:24 -05:00
85da090c2b
Output tweaks, fix day numbering
2022-06-06 15:30:58 -05:00
662d76eb7c
Bootstrap and day 1 solution
2022-06-06 15:14:31 -05:00
