I really like the merging methods and have already needed to write my own. Zach, do you mind showing a comparison of what you're thinking?
Nate, do you mind throwing this up in a gist or something? My email client isn't letting me see the whole thing. Thanks, Jason On Fri, Mar 31, 2017 at 11:52 AM Zach Waldowski via swift-evolution < [email protected]> wrote: > Snipped quoted proposal so as to not break the mailing list… By and large, > I'm in favor. I like the potential for bringing up Dictionary and Set up to > the implementation quality of Array and String. > > I don't think `init(merging:resolvingCollisionsWith:)` et al hold their > weight for inclusion in the language, unless some notable optimization > opportunity can be surfaced out of it. Users frustrated at the lack of a > `merge` in Swift want it to be opinionated and "just do the right thing," > i.e., the same way as whatever other language they most recently used. A > properly annotated and indented-to-be-beautiful use of the closure-based > version will take up the same amount of code as doing the merge by hand > with your custom condition. > > Sincerely, > Zachary Waldowski > [email protected] > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
