I am talking about what @Nevin has mentioned as well as the issue about retroactively adding a variadic overload that was mentioned earlier.
It is not clear—to me, at least—that the semantics of avoiding a forward overload is very popular. Perhaps I missed a previous discussion on it?
In any case, even if it is popular, since what is proposed is effectively a change (see my previous message), I’d argue that it has to meet the bar that the current behavior should be proved actively harmful; it’s not enough to say that, were we to do it over, we’d prefer an alternative.
I’m well aware that adding new syntax first and then applying new semantics is source-breaking. The implication, therefore, of my argument that the issues are separable is that I think we need to have a standalone discussion on changing variadic semantics before consideration of new syntax and not alongside it. This has the benefit that, if it clears the bar of showing the existing behavior is actively harmful (which is not implausible, if the argument you’re advancing is that the behavior you promote is the one that users actually expect at the callsite), then a case can be made that the same semantics should be applied to the existing syntax with appropriate automatic migration of source code.
If the new semantics can’t clear that bar, I’d argue that this proposal should not attempt to introduce such semantics.
That is a reasonable distinction, certainly. Given that there is a connection, it is worth a discussion to my mind.
No, but it is up to the community to provide feedback, which includes consideration of whether any pitches are consistent with the feel and direction of Swift. Since you’re soliciting feedback, my feedback to you is as above.