<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="">+1. I filed a radar about it months ago.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 5, 2015, at 1:24 PM, 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 class=""><br class=""></div><div class="">Thanks,</div><div class="">Alex</div><div class=""><br class=""></div><div class=""><br class=""></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=cIJNkxnlv-2FdJbDb7Mv2cwlyv1w98cwgKls0Og2NT4z-2FnHHjQSBIuC6-2BzhAlDPEqcHe-2FYHEFWznSOdmOYGdm1f-2Fsu6sXbuu3JX8cvTO9XNvXCCHPhSqEdNe-2B6rkJ9mlJ-2B3ZQubWQtVN8OP6fya-2FSsUQtr15ZuoJMClFav4pvyUpi8eemwNhPj1zBWVQZ-2F7aBZxiKyjps-2BZtrLZmOWiE8-2Bj9C4AJS9nDpU-2BKkzeLdl7tU-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
</div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></div></body></html>