Is there any appetite for allowing argument labels to be applied to the first trailing closure of a call expression? As things are now, we have to choose between indenting all closure arguments:
@xwu had a syntax for this back when trailing closures were first reviewed, and this was a huge point of contention during the review. Personally I'd still appreciate it.
There are very few places in expression grammars where two identifiers are juxtaposed, and many of them revolve around disambiguating contextual keywords (like copy x treats copy as a keyword but copy(x) treats it as an identifier). I suspect a parser rule that treats <expr> <identifier>: as a no-arg call followed by a trailing closure label would be unambiguous.
I don't remember if I mentioned it at the time, but I'm definitely for this. Every now and then I try this and and am always disappointed that it doesn't work.
That’s all that’s on the table - changes that break preexisting code are very problematic at this point, and only accepted if the problem they solve is even worse