Tootfinder

I'm so glad I'm writing the solutions in both #nim and Python because I tend to find ways to improve the Python solution with the Nim one and vice versa. Today was one of those days. The biggest thing I learned though is that solving these damned puzzles exhausted will never lead to good things quality-wise.
Solution:

This solve felt more like #nim and less like me writing Python. More uses of `map` and `apply`, using `if/then` as a proper ternary, integer -> string conversions, etc. Also the `sugar` module makes me a happy person.
The day 2 solution in Nim:

This took waaaay too long because I kept overlooking a glaring mistake at the range reduction algorithm, but once I saw it things went much more smoothly.
The #nim solution actually optimizes the range reduction step and comes in under a millisecond to execute which was nice.
Solution:

The #nim solution looks very similar to the Python one, but that works out well enough as the method works great on both. Didn't check to see if Nim had a `for/else` construction, but a friend threatened me with death if I tried.
Solution: