So I managed to get part 1 of the day, but it took 2 seconds to run on the real input, which is a bad sign.
I can’t see any kind of optimisation that means I can skip checks and know how many combinations are in those skipped checks (aside from 0.) I can bail out of branches of combinations if the info so far won’t fit, but that still leads me to visiting every valid combination which in one of the examples is 500k. (And probably way more in the input, since if I can’t complete the example near instantly the input is not happening.)
Right now I take the string, then replace the first instance of a ? with the two possible options. Check it matches the check digits so far then use recursion on those two strings.
I can try to optimise the matching, but I don’t think that solves the real problem of visiting every combination.
I don’t think (or hope) it’s just bad code but this is my code so far (python.)
edit:
spoiler
a cache was the solution!
I don’t think there are many significant optimizations with regards to reducing the search tree. It took me long enough to get behind it, but the “solution” (not saying there aren’t other ways) to part 2 is to not calculate anything more than once. Instead put partial solutions in a dict indexed by the current state and use that cached value if you need it again.
It seems like you are actually constructing all rows with replaced
?. This won’t be viable for part 2, your memory usage will explode. I have a recursive function that calls itself twice whenever a?is encountered, once assuming it’s a., and once a#.
