<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Thank you for the input, Chris!</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">I'll do my best to kickstart this project with the spirit of the core library standards and distributive it with package manager. Then maybe we could revisit closer dependency at some later date.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">PS. If anyone is interested in participating, please feel free to contact me directly.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Alex</div><div id="AppleMailSignature"><br>Sent from my iPhone</div><div><br>On Dec 6, 2015, at 7:20 AM, Chris Lattner <<a href="mailto:clattner@apple.com">clattner@apple.com</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 5, 2015, at 11:24 AM, Alexander Kolov 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=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi everyone,<div class=""><br class=""></div><div class="">Coming from a short discussion in swift-corelibs-dev, I’m investigating the need of a standard logging API as a part of core libraries.</div><div class=""><br class=""></div><div class="">The motivation behind this would be having a unified and configurable set of APIs between all first-party modules and third party applications and libraries.</div><div class="">I think this will help each of us since right now we’re inventing our own solutions as well many bigger third-party library providers have formats and facilities of their own.</div><div class=""><br class=""></div><div class="">As I currently see it would be somewhat similar to python logging and possibly even structlog (<a href="http://www.structlog.org/en/stable/" class="">http://www.structlog.org/en/stable/</a>), with configurable formatters and handlers, including and not limited to remote loggers and syslog support.</div><div class=""><br class=""></div><div class="">I’d love to hear your opinions and feedback on this and possibly start with some more formalized proposal and implementation if there’s enough support and need.</div></div></div></blockquote><br class=""></div><div>Hi Alex,</div><div><br class=""></div><div>At this point, we’d prefer that major new features like these be explored and developed as independent projects outside the official Swift repos. There are a *ton* of really interesting library features that we could add, but for now at least, we’re keeping the Swift standard library laser focused on its “language features + core data structures & algorithms” focus, and keeping the CoreLibs work focused on achieving parity with the Apple implementations of these libraries.</div><div><br class=""></div><div>We simply don’t have bandwidth to review and design higher level features at this time. One of the goals of the Swift package manager is to make it super easy to reuse people’s code, even if it isn’t part of the swift distro.</div><div><br class=""></div><div>-Chris</div><br class=""></div></blockquote></body></html>