[swift-evolution] [Idea] Passing an Array to Variadic Functions

Dave Abrahams dabrahams at apple.com
Wed Apr 20 15:08:56 CDT 2016

on Wed Apr 20 2016, Dave Abrahams <swift-evolution at swift.org> wrote:

> on Wed Apr 20 2016, Tino Heth <swift-evolution at swift.org> wrote:
>>> 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?").
> We're in a stage of Swift's development where we can ask this question
> fairly freely, and the fact that we expect to reach stability soon,

I should clarify that this is true for a sufficiently-nebulous
definition of “soon.” :-)

> where it will be harder to ask the question, makes us ask it a bit
> more often these days.  It's a balance; we don't want to create
> arbitrary language churn, but we also don't want to be forever stuck
> with decisions we'll regret later.


More information about the swift-evolution mailing list