Replies: 2 comments
-
|
@fclairamb yes I think we should switch in the future, once we can drop support for Go 1.20 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I'm thinking about keeping only compatibility with the two last releases. Most libraries do that. The rationale is that upgrading Go is a low-effort task. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This is mostly for @drakkan, but everyone else is welcome
I created the go-log library because there was no standard library for structured logging in Go. This allowed us to create a common definition with some bindings to the most common structured logging libraries.
But since we now have one (log/slog), we should most probably switch to log/slog.
What do you think ?
1 vote ·
Beta Was this translation helpful? Give feedback.
All reactions