This is how it starts. First you're passing out arrays and using Ruby's destructuring shortcut.
Then you're noticing other languages have true multiple returns. You begin hankering after neat little error handling idioms and useful state machine hacks. You begin tinkering with Lua or various Lisps.
But soon that's not enough. You find yourself huffing full blown pattern matching operators and dissing statefulness. You'd ask for an intervention from friends, but that would require I/O. You're doomed.
What really hooked me on destructuring and argument pattern matching was a sophomore year lecture on red black trees in ML. The rotation function was implemented multiple times with different patterns matching the different local tree structures that needed rotating. Much much more elegant than any other implementation of that they I've ever seen.
FWIW all of those examples work in Python 3 as well. The language was extended with PEP 3132[1] to support "extended iterable unpacking" (I wish they would just call them "splats").
Python doesn't have a `values_at` method, though `map(hash.get, keys)` or `[hash[key] for key in keys]` isn't too bad.
Then you're noticing other languages have true multiple returns. You begin hankering after neat little error handling idioms and useful state machine hacks. You begin tinkering with Lua or various Lisps.
But soon that's not enough. You find yourself huffing full blown pattern matching operators and dissing statefulness. You'd ask for an intervention from friends, but that would require I/O. You're doomed.