Because many APIs use configuration/partial initialisation patterns. Look at Metal for example. But I agree that most of the time, its not such a big deal.
— Taras > On 13 Apr 2016, at 17:34, Kurt Werle <[email protected]> wrote: > > I've always thought that the with construct is not a good idea. It seems to > me that the moment you want to use with it indicates that you are getting too > much into some other classes business; shouldn't that class deal with this? > Why are you exposing/integrating so much of some other class's logic? Maybe > there should be a method that does all this, or maybe a custom struct that > passes all the appropriate information... > > Yeah, there are exceptions - always. But for the most part I'm not a fan. > > Kurt > -- > [email protected] > http://www.CircleW.org/kurt/ <http://www.circlew.org/kurt/>
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
