[feature-request] Allow implicit function application syntax for nested index expressions

Currently

# we can do
ys = list(map(.[0], xs))
# and
ys = list(map(.[0, 1], xs))
# but not
ys = list(map(.[0][1], xs))

This nesting is supported in the case of attrgetter, but not itemgetter. Instead of compiling to a closure (which we have to do by hand right now, anyway), it can instead compile to an expression of a new built-in function that basically does a ‘nested-get’ on __getitem__-able objects.

[evhub]

@narfanar As a simple workaround, you could do

ys = list(map(.[0] ..> .[1], xs))

which is probably what .[0][1] will get compiled to if this gets implemented.

[pavelbraginskiy]

If this is implemented I think .[x].someattr[y].otherattr or other arbitrary combination of indexing and attribute access should be allowed.