advent-of-clojure VS advent-of-code

Clojure: https://github.com/motform/advent-of-clojure/blob/master/src/advent_of_clojure/2022/06.clj

Clojure, quite happy with this one, simply using a stack and the assumptions we know about the input to easily compare, filter and then match.

Clojure, for sure my worst one yet. BUT, I did get to use `clojure.set/invert-map` twice, so I count that as a partial win.

Clojure, using (almost) exclusively set logic. Looking at the other solutions, it could have probably been simplified, but I'm somehow compelled to use sets whenever I get the chance.

Very similar to mine, clearly the platonic Clojure solution to the problem.

Clojure, mainly list manipulation and `core`.

Scala using µJson. Really happy with how concise this is. I was able to parse everything into a Packet class that extends Ordered, which gives us the compare function. So once that was implemented recursively according to the rules we were given, I was able to jsut call .sorted for part 2.

Scala using jgrapht. I thought part 2 would require a different graph (similar to 2018 day 22) since the story said "to avoid needing to get out your climbing gear..." Glad that wasn't the case!

Scala. Pretty happy with how I parsed these into anonymous instances of my Monkey trait. For me part 2 wasn't hard because of the modulo trick, but because I was using mutable queues. So I had to add a reset() method to get things back the way they were before running part 2

Scala using tail recursion. Not the prettiest, but it works

Scala. Not too bad with my Point helper class. After part 1 I refactored the movements into a move helper that just takes 2 arbitrary points; the current point and the one we are moving towards. Then it was easy enough to just apply that in order each iteration for part 2.

Scala. It's ugly, but it works ¯\_(ツ)_/¯

Scala. Parsing wasn't as hard as I thought it would be using transpose and then just filtering non-alphanumeric characters. I initially parsed to a Map[Int, mutable.Stack[Char]] but then that bit me in part 2 when I would have to "reset" it (dang mutability!). So instead I parse to Map[Int, String] and just build the mutable stacks twice.

Updated version using sets instead of ranges

Scala. A little more verbose than I would like, but it works ¯\_(ツ)_/¯

Scala