<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 class="">Sound great! </div><div class=""><br class=""></div><div class="">Last week I started working on a pure-swift graphics library, one goal being fast server-side graphics manipulations, and already have .png decode/encode, and quadratic bezier curve stroking implemented, slowly, and poorly. I’m working on TrueType fonts right now, and intend to open it to other developers once the basic architecture is refined. I intend to add SVG and JPEG support as well. It seems like if there is a “swift-community blessed geometry library”, this would be a natural extension of that, or at least depend on it.</div><div class=""><br class=""></div><div class="">Much of this depends on compression support, which I’ve already published a first cut of at <a href="https://github.com/benspratling4/SwiftFoundationCompression" class="">https://github.com/benspratling4/SwiftFoundationCompression</a> . The goal there was a more “foundation” idea of compression than competing libraries, but it suffers from a lack of streaming support.</div><div class=""><br class=""></div><div class="">I would absolutely love a “BigNum” library. Several encryption packages out there would benefit from it as well. It seems arithmetic compression libraries would benefit, too. Other useful Numeric types would include rational fractions, fixed-point, and short floats (Float16 is what Apple now thinks the future of images is, right?). I’m happy to contribute; I end up writing those in a new language ever few years anyway.</div><div class=""><br class=""></div><div class="">-Ben Spratling</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 7, 2017, at 12:54 PM, Dave DeLong via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Swift-Evolution,<br class="">...<br class=""><br class="">We propose to create an open-sourced "Non-Standard Library" effort that coexists with, coordinates with, and is blessed by the open source Swift development community. The "Non-Standard Library" will offer a well-curated, high-value collection of routines, types, and documentation to support Swift development on all platforms.<br class="">…</div></div></blockquote><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><b class="">Suggested Libraries</b><br class=""><br class="">There are several areas we think that are ripe for improvement and implementation as a non-standard library, such as (but not limited to):<br class=""><div class=""><ul class=""><li class="">A BigNum library</li><li class="">A full-featured Random library</li><li class="">A simplified date/time library</li><li class="">A library for manipulating paths (that is not based on URL or String)</li><li class="">An expanded Swift-native Geometry library and so forth.</li></ul></div>The scope and extent of the sublibraries would be proposed and debated on a parallel Non-Standard Library Evolution development list.<br class=""></div></div></blockquote></div><br class=""></body></html>