3 ms·

>This "foo" still suffers from the same problem as "Option::map" does: it is hard-coded for functions of fixed arity (2 in this case, 1 in Option::map's case).

>This "foo" still suffers from the same problem as "Option::map" does: it is hard-coded for functions of fixed arity (2 in this case, 1 in Option::map's case). Hence the last paragraph in my comment.

yakubin 5y ago
Sorry. I didn't see it before. You're right.
- Arnavion 5y ago
  Actually, I'm sorry too. I just realized I had a brainfart while writing that example and forgot to make the point I wanted to make. I've fixed it now. (It was supposed to work with any-arity tuples as well.)