<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><br class=""><blockquote type="cite" class=""><div class=""><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Not even just for development… a standard repository for “substandard” library(s) would be a great for commonly used types that aren’t quite commonly used enough to include in stdlib, and IMHO, could really help Swift’s ecosystem (I’m not claiming that it’s poor now or anything, but there’s nothing wrong with making it the best we can).</div></div></blockquote></div>There have been attempts to establish exactly that (I'd describe it as "Boost for Swift"), but without at least a tiny bit of support from Core, such plans imho won't be successful:<div class="">It's way to easy to start your own "substandard"...</div><div class=""><br class=""></div><div class="">My favourite example why this would be beneficial are quaternions, which have several implementations in different Apple frameworks :-( — and there are a lot of really simple datatypes and functions which might be implemented over and over, all doing nearly identical things, but none of them compatible with each other.</div></body></html>