> The question is whether the downside to variadic parameters is really enough
> to justify _removing_ an existing language feature.
>
> The burden of justification should be on those people wanting to change the
> language, not on those wanting to maintain the status quo and “I don’t like
> it” or “I think it makes code a tiny bit less readable” is not sufficient
> justification, in my opinion because you already have the option not to use
> the feature.
Afaics, this isn't true:
Increment/decrement operators, currying, tuple splat and even the C-style for
loop have already been deprecated, and although I would have preferred to keep
some of those constructs, I think it is good how progressive Swift is pushed
forward ("would we add this feature now if it wasn't already there?").
The value of variadic functions is imho less than the possibility to omit "()"
in procedure calls, and afair, there have been several posts that illustrate
the complications of this feature.
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
