<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div>On Dec 26, 2016, at 11:12, Tino Heth via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8">There is an older discussion that is somewhat linked to this topic:<div class="">"Removing the empty initialiser requirement from RangeReplaceableCollection"<br class=""><div class=""><a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160704/023642.html" class="">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160704/023642.html</a></div><div class=""><br class=""></div></div><div class="">Imho "DefaultConstructible" types can be very handy, but so far, it seems no one has presented a single use case that is important enough to justify the inclusion in the stdlib.</div><div class="">On the other hand, I'm quite sure that there's much functionality in the stdlib that many people consider as superfluous…</div><div class=""><br class=""></div><div class="">I guess adding the protocol wouldn't have a big impact on size, so for for me, the question is "Does this protocol confuse users of Swift?", which I'd answer with "yes, possibly" (unless someone comes up with a name that is more intuitive).</div></div></blockquote><br><div>"Identity", but, at least for many numeric types, you'd need a mechanism for specifying which one you mean.</div><div><br></div><div>- Dave Sweeris</div></body></html>