<div>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? </div><div><br></div><div>Nate, do you mind throwing this up in a gist or something? My email client isn't letting me see the whole thing. </div><div><br></div><div>Thanks, </div><div>Jason</div><div><br></div><div><br><div class="gmail_quote"><div>On Fri, Mar 31, 2017 at 11:52 AM Zach Waldowski via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u class="gmail_msg"></u>
<div class="gmail_msg"><div style="font-family:Arial" class="gmail_msg">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.<br class="gmail_msg"></div>
<div style="font-family:Arial" class="gmail_msg"><br class="gmail_msg"></div>
<div style="font-family:Arial" class="gmail_msg">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. <br class="gmail_msg"></div>
<div style="font-family:Arial" class="gmail_msg"><br class="gmail_msg"></div>
<div id="m_-6106093374295642008sig40804545" class="gmail_msg"><div class="m_-6106093374295642008signature gmail_msg"><span class="m_-6106093374295642008font gmail_msg" style="font-family:arial,sans-serif,sans-serif">Sincerely,</span><span class="m_-6106093374295642008font gmail_msg" style="font-family:arial,sans-serif,sans-serif"></span><br class="gmail_msg"></div>
<div class="m_-6106093374295642008signature gmail_msg"><span class="m_-6106093374295642008font gmail_msg" style="font-family:arial,sans-serif,sans-serif"> Zachary Waldowski</span><span class="m_-6106093374295642008font gmail_msg" style="font-family:arial,sans-serif,sans-serif"></span><br class="gmail_msg"></div>
<div class="m_-6106093374295642008signature gmail_msg"><span class="m_-6106093374295642008font gmail_msg" style="font-family:arial,sans-serif,sans-serif"> </span><a href="mailto:zach@waldowski.me" class="gmail_msg" target="_blank"><span class="m_-6106093374295642008font gmail_msg" style="font-family:arial,sans-serif,sans-serif">zach@waldowski.me</span></a><br class="gmail_msg"></div>
</div>
<div class="gmail_msg"><br class="gmail_msg"></div>
</div>
_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div></div>