Last time, I introduced the tadpole operators. As you have probably figured out by now, it was a joke. There are no new tadpole operators. […] The tadpole operators are pseudo-operators, like the goes to operator or the sproing operator: They take advantage of existing language features, and come with a creative story.
To see x[0]->y as an operator on two things, instead of two operators on three things is more than just an interesting trick: One of the most important skills a programmer develops is the taste to decide how big the chunk should be. If it’s too large, then it may contain such a large idea that it can’t be composed, but if it’s too small then you end up with a lot of supersequence repetition (often easiest to see in a concatenative language). Learning how to invent new operators is key to producing more succinct code.
I love these composite “operators” in the C world, another one is the “goes to” operator:
See also: The tadpole operator,
What?? That is a joke, right?
At the cost of ruining it:
https://blogs.msdn.microsoft.com/oldnewthing/20150526-00/?p=45034/
Ah, thanks for the explanation :P
Actually, according to this kind of a joke post, it should be:
Note the single -.
To see
x[0]->yas an operator on two things, instead of two operators on three things is more than just an interesting trick: One of the most important skills a programmer develops is the taste to decide how big the chunk should be. If it’s too large, then it may contain such a large idea that it can’t be composed, but if it’s too small then you end up with a lot of supersequence repetition (often easiest to see in a concatenative language). Learning how to invent new operators is key to producing more succinct code.