Andy Ferris

Really cool :) @ararslan The behavior you highlight as odd seems natural to me. (An aside: what is an unbracketed `Generator` ambiguous with, or stated another way, why does it...

> I think it would be short-sighted to tie currying syntax to piping syntax. It's possible that the reason piping has been raised is that there was a proposal (e.g....

@stevengj Agreed - I personally feel that overall this PR is much better than that idea (I did however think it was worth mentioning the earlier discussions/thoughts on piping, for...

> seems like it may expose some implementation details of lowering A bit of an aside, but I feel that the details of lowering should be straightforward and understandable. I've...

Like Jacob, I have also been wanting to use this feature quite a lot lately. Things like AcceleratedArrays already rely heavily on the new currying of a few select functions...

The hard thing here is that we really need users to be able to read code and more-or-less instantly predict what it will do. I'm guessing that unless we have...

Personally, that might drive me crazy... Yes it would be convenient to *write* code like that, but hell no I don't want to *read* other people's code written like that,...

> The same argument can be brought against all kinds of function overloading. I can define getindex to mean something crazy for my custom types. But I shouldn't and I...

> We know TypedTables will fail That PR is merged and tagged now

Sorry - I'm a bit behind and am still trying to understand this. I'm happy to try and help. However, I'm a little lost what is being asked for? If...