<div dir="ltr"><div>> <span style="font-size:12.8px">*Which* APIs become more ergonomic?</span></div><div><span style="font-size:12.8px"><br></span></div><div>I'll get back to this question in a second if I may. This would be a longer discussion and I first want to make sure that before we get into the details that there is a possibility of this being introduced (I'm asking if violating the no zero defaults is more important than slightly more ergonomic APIs). But to give a broad answer I think that the concept of a zero is closely related to the concept of equality (and all the things that build up on equality such as comparability and negation). </div><div><br></div><div>> <span style="font-size:12.8px">1) How does this square with Swift’s general philosophy to not default initialize values to “zero”?</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">I actually wasn't aware of this philosophy. Despite this philosophy, look at how many types actually currently implement a default constructor. Also can I ask what's the motivation behind this philosophy? </span></div><div><span style="font-size:12.8px">I think that in Swift, default constructibility makes complete sense for (most?) structs, maybe less so for classes. </span></div><div><br></div>> <span style="font-size:12.8px">2) To your original example, it isn’t immediately clear to me that reduce should choose a default identity. Some types (e.g. integers and FP) belong to multiple different ring algebras, and therefore have different identity values that correspond to the relevant binary operations.</span><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">This is a good point that I've considered as well but felt that for the most part, there is one particular identity and associated operation that is more prominent and useful than others. Furthermore, modeling different algebras isn't mutually exclusive with writing generic algorithms that rely on this protocol, you can always introduce some monoidic wrapper type that defines the more appropriate default value and operation.</span></div><div><span style="font-size:12.8px"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 25, 2016 at 1:24 PM, Chris Lattner <span dir="ltr"><<a href="mailto:clattner@apple.com" target="_blank">clattner@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><span class="">On Dec 25, 2016, at 12:54 PM, Adam Nemecek via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</span><div><span class=""><blockquote type="cite"><div><div dir="ltr">Does enabling a lot of small improvements that make APIs more ergonomic count as practical?</div></div></blockquote><div><br></div></span><div>Yes, that would count as practical, but Xiaodi’s question is just as important. *Which* APIs become more ergonomic?</div><div><br></div><div>Here are a couple of more questions:</div><div><br></div><div>1) How does this square with Swift’s general philosophy to not default initialize values to “zero”?</div><div><br></div><div>2) To your original example, it isn’t immediately clear to me that reduce should choose a default identity. Some types (e.g. integers and FP) belong to multiple different ring algebras, and therefore have different identity values that correspond to the relevant binary operations.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>-Chris</div></font></span><div><div class="h5"><br><blockquote type="cite"><div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 25, 2016 at 12:19 PM, Xiaodi Wu <span dir="ltr"><<a href="mailto:xiaodi.wu@gmail.com" target="_blank">xiaodi.wu@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span>On Sun, Dec 25, 2016 at 3:07 PM, Adam Nemecek <span dir="ltr"><<a href="mailto:adamnemecek@gmail.com" target="_blank">adamnemecek@gmail.com</a>></span> wrote:<br></span><div class="gmail_extra"><div class="gmail_quote"><span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">There's a book that provides quite a bit of info on this <div><br></div><div><a href="https://smile.amazon.com/Elements-Programming-Alexander-Stepanov/dp/032163537X?sa-no-redirect=1" target="_blank">https://smile.amazon.com/Eleme<wbr>nts-Programming-Alexander-Step<wbr>anov/dp/032163537X?sa-no-redir<wbr>ect=1</a><br></div><div><br></div><div>They say that DefaultConstructible is one of the essential protocols on which most algorithms rely in one way or another. One of the authors is the designer of the C++ STL and basically the father of modern generics.</div><div><br></div><div>This protocol is important for any algebraic structure that deals with the concept of appending or addition (as "zero" is one of the requirements of monoid). There isn't a good short answer to your question. It's a building block of algorithms. Think about why a RangeReplaceableCollection can provide you with a default constructor but a Collection can't. </div><div><span style="color:rgb(80,0,80)"></span></div></div></blockquote><div><br></div></span><div>It's well and fine that most algorithms rely on the concept in one way or another. Yet the Swift standard library already implements many generic algorithms but has no DefaultConstructible, presumably because there are other protocols that guarantee `init()` and the algorithms being implemented don't need to be (practically speaking) generic over all DefaultConstructible types. My question is: what practical use cases are there for an explicit DefaultConstructible that are impractical today?</div><span><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><span style="color:rgb(80,0,80)">On Sun, Dec 25, 2016 at 11:37 AM, Xiaodi Wu </span><span dir="ltr" style="color:rgb(80,0,80)"><<a href="mailto:xiaodi.wu@gmail.com" target="_blank">xiaodi.wu@gmail.com</a>></span><span style="color:rgb(80,0,80)"> wrote:</span><br></div></div><div class="m_-267952324834337685m_8912025549324475289HOEnZb"><div class="m_-267952324834337685m_8912025549324475289h5"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Can you give some other examples of generic algorithms that would make use of this DefaultConstructible? I'm having trouble coming up with any other than reduce.<br><div class="gmail_quote"><div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951h5"><div dir="ltr">On Sun, Dec 25, 2016 at 14:23 Adam Nemecek via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951h5"><div dir="ltr" class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg">This protocol is present in C++ <a href="http://en.cppreference.com/w/cpp/concept/DefaultConstructible" class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg" target="_blank">http://en.cppreference.com<wbr>/w/cpp/concept/DefaultConstruc<wbr>tible</a> as well as in Rust <a href="https://doc.rust-lang.org/std/default/" class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg" target="_blank">https://doc.rust-lang.org/std/<wbr>default/</a><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"><br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"></div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg">It's the identity element/unit of a monoid or a zero.<br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"><br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"></div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg">The Swift implementation is very simple (I'm open to different names)<br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"></div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"><br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"></div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg">protocol DefaultConstructible {</div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"> init() </div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg">}</div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"><br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"></div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg">A lot of the standard types could then be made to conform to this protocol. These include all the numeric types, collection types (array, set, dict), string, basically at least every type that currently has a constructor without any arguments.</div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"><br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"></div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg">The RangeReplaceableCollection protocol would inherit from this protocol as well. <br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"></div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"><br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"></div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg">This protocol would simplify a lot of generic algorithms where you need the concept of a zero (which shows up a lot)</div></div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"><br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"></div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg">Once introduced, Sequence could define an alternative implementation of reduce where the initial result doesn't need to be provided as it can be default constructed.</div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"><br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"></div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"><br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"></div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"><br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"></div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"><br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"></div><div class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"><br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg"></div></div></div></div></div>
______________________________<wbr>_________________<br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg">
swift-evolution mailing list<br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg" target="_blank">https://lists.swift.org/mailma<wbr>n/listinfo/swift-evolution</a><br class="m_-267952324834337685m_8912025549324475289m_699475458640075951m_-6015751673947924360gmail_msg">
</blockquote></div>
</blockquote></div><br></div>
</div></div></blockquote></span></div><br></div></div>
</blockquote></div><br></div>
______________________________<wbr>_________________<br>swift-evolution mailing list<br><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br></div></blockquote></div></div></div><br></div></blockquote></div><br></div>