SE-0279: Multiple Trailing Closures [Amended]

[Lantua]

I think we should maintain the stance that Swift is (largely) agnostic to the choice of whitespace. Esp. that this is still valid:

// well
func
// umm
foo1
// anyway
(
// this is fine
a:
//
Int) { }

We can agree that no one writes like this. Still, fixing that is probably way out of scope of this proposal. It's more important to figure out a structure that we can encourage, and enforced via style guide.

@John_McCall

If you think the current SE-0279 proposal can work on its own but you’d prefer it to go further in certain ways, that’s very interesting feedback. Likewise if you think it’s not a good idea unless it does go further. It’s not an up/down vote; you don’t have to try to distill your conclusions down to a single bit.

I want to added my thoughts on this... too. Since function-with-multiple-closure is a largely untouched api space and all. Which ever syntax we go with, the apis will start optimising toward the syntax, and likely away from similar syntaxes. While of course no one can predict the future, we probably want to be more careful than letting it out, then adjust it later.