While definitely great proof of:
1. The author knowing a lot of the language's functional features
(permutations, mapping, zipping, filters)
2. How powerful functional programming is when solving problems<p>I find this type of code an anti pattern of how good code should be.
This solution has a high "cognitive load" imho:
<a href="http://chrismm.com/blog/how-to-reduce-the-cognitive-load-of-your-code/" rel="nofollow">http://chrismm.com/blog/how-to-reduce-the-cognitive-load-of-...</a><p>I'd much rather see a 15-20 line solution that's clear and readable, than a 4 line solution that I have to reverse engineer.