Yes, absolutely this - I'd likely be fine with the order of them being strict, but being able to omit ones that I want to be defaulted is a must.
l8r Sean Sent from my iPhone > On Mar 30, 2016, at 12:06 PM, William Dillon via swift-evolution > <swift-evolution@swift.org> wrote: > > As long as you can still provide an overriding value to only one of the > defaulted parameters I probably wouldn't miss it. I would hate to have to > re-state the default value of all the parameters up to the one I want to > change, though. > > - Will > >> On Mar 30, 2016, at 9:59 AM, Joe Groff via swift-evolution >> <swift-evolution@swift.org> wrote: >> >> Many people are surprised when they find out defaulted parameters can be >> reordered, unlike required arguments. This special case adds complexity to >> the language, and runs against our general trend of treating argument labels >> as a significant part of an API's name, and preferring a single way of >> writing API calls. I think it's worth revisiting this design choice—is the >> special case worth the complexity? How many people take advantage of default >> argument reordering? >> >> -Joe >> _______________________________________________ >> swift-evolution mailing list >> swift-evolution@swift.org >> https://lists.swift.org/mailman/listinfo/swift-evolution > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
