Day 19 is definitely my proudest solve (though learning about Aho-Corasick dampens it a little bit 😅) with some clever ideas to both check towels more efficiently than the naïve approach while creating no String
s to avoid a bunch of heap allocation. Figuring out how to binary search without creating the target object, and merely knowledge of its properties and those of the list, meant I got to use a pretty niche library function and got my solution from 25 to 11 ms.
EnEnCode
Congrats to everyone! Not first year, though first year of at least trying every problem. Burnout definitely got me by day 20 though, ha ha ha...
There was a lot of ugly (readability a backseat to "code writing speed"), a lot of bad (don't ask how long the test suite has to run for), but an occasional gem of good (my day 19 solution is some of the most dopamine from just writing code I've gotten. I'm only used to getting that much when it actually gets merged).
I learned a little through the problems themselves, but I did learn a lot about writing macro_rules
macros by creating a test suite generator and a benchmark generator. I also picked up some useful Git knowledge like --allow-unrelated-histories
, interactive rebasing, --name-only
, and using the reflog to help recover data (don't ask what happened on day 23).
This year was a personal success. Till next year!
Rust
Definitely not Aho–Corasick cool or genius, but does get ~11ms on both parts. Gains over the other Rust solves are partly a less naïve approach to towel checking and partly getting it to work with 0
String
allocations, which involves both an instructive lifetime annotation and the clever use of a niche standard library function.Code