You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
So I think treating transforms like normal functions is actually a mistake, at least if you want to get performance-conscious people to adopt them. What I really want is a way to *denote* a block of code as "a map piped into a filter" and have lots of nice tooling around that.
(Macros, I think, are not the right choice here either: it's still difficult to chain them efficiently, and they tempt you to reuse a single generic-but-suboptimal implementation of each transform.)
I guess there's a fundamental trade-off here: if you merely *denote* a block of code as a map transform, you might be mistaken, whereas a map function will definitely be a map function.
At any rate, it seems like like there's an opportunity for a new systems language to provide dataflow-style constructs without having to compromise on performance; and perhaps this could be accomplished via tooling moreso than syntax.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
