[swift-evolution] Proposal: standard logging facility

Chris Lattner clattner at apple.com
Sun Dec 6 00:20:05 CST 2015


> On Dec 5, 2015, at 11:24 AM, Alexander Kolov via swift-evolution <swift-evolution at swift.org> wrote:
> 
> Hi everyone,
> 
> 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.
> 
> 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.
> 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.
> 
> As I currently see it would be somewhat similar to python logging and possibly even structlog (http://www.structlog.org/en/stable/ <http://www.structlog.org/en/stable/>), with configurable formatters and handlers, including and not limited to remote loggers and syslog support.
> 
> 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.

Hi Alex,

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.

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.

-Chris

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151205/1fa169b4/attachment.html>


More information about the swift-evolution mailing list