Re: [go-nuts] Logging best practices with log/slog

> On Apr 1, 2025, at 3:50 AM, robert engels wrote: > > I don’t think this is that complicated. ... > > slog already has the infrastructure to support additional handlers which I > think is all that is needed to support custom requirements - aka side effects > - of external libraries. Hmm. Ok

Re: [go-nuts] Logging best practices with log/slog

I don’t think this is that complicated. The go team can change the implementation of both log to delegate to slog with some defaults. slog already has the infrastructure to support additional handlers which I think is all that is needed to support custom requirements - aka side effects - of ext

Re: [go-nuts] Logging best practices with log/slog

> On Mar 30, 2025, at 3:45 AM, Andrew Harris wrote: > > > Can you link that discussion, please, for those of us who may have not seen > > the discussion nor be able to find the specific discussion via search? > > https://github.com/golang/go/issues/56345 >

Re: [go-nuts] Logging best practices with log/slog

> Can you link that discussion, please, for those of us who may have not seen the discussion nor be able to find the specific discussion via search? https://github.com/golang/go/issues/56345 (super-thread) https://github.com/golang/go/issues/58243 (what to do about context) There's more scattere

Re: [go-nuts] Logging best practices with log/slog

> On Mar 28, 2025, at 8:58 AM, cpu...@gmail.com wrote: > > I'm in the process of converting our application (evcc.io) from using > spf13/jwalterweatherman for logging to log/slog. This is a very serendipitously timed discussion (for me) since yesterday and today I have been working on how to

[go-nuts] Logging best practices with log/slog

I'm in the process of converting our application (evcc.io) from using spf13/jwalterweatherman for logging to log/slog. One current pain point is passing loggers around the application and deriving child loggers. With using slog there are various options for doing that: Passing loggers: - pa