[swift-evolution] [Review] SE-0060: Enforcing order of defaulted parameters

Dave Abrahams dabrahams at apple.com
Thu May 5 20:55:15 CDT 2016

on Wed May 04 2016, Erica Sadun <swift-evolution at swift.org> wrote:

> Having to figure out where a previously defaulted value should be inserted when
> adding an explicit setting imposes an undue burden on the programmer, reduces
> flexibility during experimentation, and removes one of the neatest Swift
> features. For this reason, I vote no on the proposal. By rejecting this
> proposal, Swift retains a flexibility that defers to the programmer, placing the
> programmer's needs before any benefits that may accrue to the compiler.
> I have followed the discussion. I believe it goes against the general Swift
> philosophy. And while the change being proposed is significant to be part of a
> formal language review process, I think adopting it would be the wrong thing to
> do.
> -- Erica

FWIW, Erica echoes my instincts on the topic.


More information about the swift-evolution mailing list