Pitch: Syntactic sugar for circumventing closure capture lists

@sveinhal unfortunately, I come across the case fairly frequently where I really do need access to self within the body of the closure (hence the capture lists).

I should should clarify, that this would still 'capture' self, it's simply a shorthand way of defining a closure which refers to an instance method of any arity, whilst capturing self as 'unowned'.

Essentially a macro for { [unowned self] in self.instanceMethod($0...,$n) }.