<div dir="ltr">I was thinking about the requirements to make this happen. It only needs someone to do the initial organization. So I created a GitHub organization and put up a couple projects. The Matrix4 project is feature-complete. The Complex project is just a foothold.<div><br></div><div>Now we need more projects. The readme in the contrib project has information about getting your project added.<div><br></div><div><a href="https://github.com/swift-breeze">https://github.com/swift-breeze</a></div><div><br></div><div>-david<br></div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 26, 2016 at 3:51 PM, Matthew Johnson via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word">+1. I have already suggested that we have a space for libraries that get reviewed by the community but are distributed by SPM rather than being part of stdlib and corelibs.<div><div><div><br><div><br><div><blockquote type="cite"><div>On Jan 26, 2016, at 5:48 PM, Howard Lovatt via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br><div>This is a good idea. It will be a lot easier with the module system, particularly if that system is searchable so that you have a chance of finding that someone has already written what you want.<br><br>On Wednesday, 27 January 2016, Trent Nadeau via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">This is similar to Rust's nursery (<a href="https://github.com/rust-lang-nursery" target="_blank">https://github.com/rust-lang-nursery</a>) that contains commonly used libraries (logging, UUIDs, etc). These are under Rust's umbrella but aren't part of the standard library and can be versioned separately but still go through a similar stdlib process. If libraries in the nursery become very widely used, then an RFC can come in requesting for it to be added to the stdlib, and most libraries need to be in the nursery before they can be added to the stdlib.<div><br></div><div>I think an approach like that would work well for Swift.</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 26, 2016 at 6:32 PM, Tino Heth via swift-evolution <span dir="ltr"><<a>swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="auto"><div><span></span></div><div><div><span></span></div><div>There have been several threads to add specific functions or types to the stdlib:<div>- <span style="font-family:'Helvetica Neue'">Either in the Swift Standard Library</span></div><div><span style="font-family:'Helvetica Neue'">- </span><span style="font-family:'Helvetica Neue'">Proposal: Add scan, takeWhile, dropWhile, and iterate to the stdlib</span></div><div><span style="font-family:'Helvetica Neue'">- Higher Kinded Types (Monads, Functors, etc.)</span></div><div><span style="font-family:'Helvetica Neue'">- </span><span style="color:rgb(76,76,76);font-family:'Helvetica Neue'">Adding a new filter method which returns 2 arrays</span></div><div><span style="color:rgb(76,76,76);font-family:'Helvetica Neue'">- </span><span style="font-family:'Helvetica Neue'">Add replace(_:with:) function to the stdlib</span></div><div><span style="font-family:'Helvetica Neue'">- map-like operation that returns a dictionary</span></div><div><span style="font-family:'Helvetica Neue'">- </span><span style="font-family:'Helvetica Neue'">Rectangles and other common structures.</span></div><div><span style="font-family:'Helvetica Neue'">- </span><span style="font-family:'Helvetica Neue'">Add zip2WithNilPadding function</span></div><div><span style="font-family:'Helvetica Neue'">- </span><span style="font-family:'Helvetica Neue'">Add types BufferedSequence, BufferedGenerator</span></div><div><font face="Helvetica Neue">- … (guess there are some that I missed — I didn't look at last years threads at all).</font></div><div><font face="Helvetica Neue"><br></font></div><div><font face="Helvetica Neue">Afair, none of those ideas turned into real proposals, and I think that keeping stdlib small is a good goal.</font></div><div><font face="Helvetica Neue"><br></font></div><div><font face="Helvetica Neue">Nonetheless, there are plenty of data structures and algorithms that will be used in many places by many different teams, and each of them might write its own implementation. That's imho no big problem for algorithms, but for types, it will most likely lead to real annoyance.</font></div><div><font face="Helvetica Neue"><br></font></div><div><font face="Helvetica Neue">I hope that we will soon have a great package manager for Swift, but I don't think that will solve this issue completely:</font></div></div><div><font face="Helvetica Neue">I wouldn't import a big third-party framework just because a tiny function like "dropWhile" could make my code more elegant...</font></div><div><font face="Helvetica Neue"><br></font></div><div><font face="Helvetica Neue">Of course, some widely accepted libs might rise and improve interoperability, but it is hard to predict how our ecosystem will evolve, and you don't have to wait for the future to see the what could happen when there is no common base</font><font face="Helvetica Neue">:</font></div><div><span style="font-family:'Helvetica Neue'">Just take a look at SCNQuaternion, GLQuaternion and CMQuaternion.</span></div><div><br></div><div><span style="font-family:'Helvetica Neue'">Instead of asking to pollute stdlib with stuff like 3d transformations, I'd prefer a set of general purpose libraries under supervision by the Swift team:</span></div><div><span style="font-family:'Helvetica Neue'">It could be a great way for "outsiders" to get into Swift development, and most likely wouldn't put to much stress and responsibility on the shoulders of each "manager".</span></div><div><font face="Helvetica Neue">It also could take pressure from the stdlib (and this mailinglist :)</font></div><div><font face="Helvetica Neue"><br></font></div><div><font face="Helvetica Neue">Beside fields of application (graphics, images, music, algebra, statistics, pattern matching, machine learning, graph theorie... whatever raises enough interest), there could also be libraries to support concepts like functional programming.</font></div><div><font face="Helvetica Neue"><br></font></div><div><font face="Helvetica Neue">Best regards,</font></div><div><font face="Helvetica Neue">Tino</font></div></div><div><br></div></div><br>_______________________________________________<br>
swift-evolution mailing list<br>
<a>swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Trent Nadeau</div>
</div></div>
</blockquote><br><br>-- <br> -- Howard.<br><br>
_______________________________________________<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/mailman/listinfo/swift-evolution</a><br></div></blockquote></div><br></div></div></div></div></div><br>_______________________________________________<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" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div></div></div></div>