-
Notifications
You must be signed in to change notification settings - Fork 18.2k
log: improve logger implementation #48464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
log: improve logger implementation #48464
Conversation
This PR (HEAD: 20c4f5b) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/go/+/350869 to see it. Tip: You can toggle comments from me using the |
Message from Go Bot: Patch Set 1: Congratulations on opening your first change. Thank you for your contribution! Next steps: Most changes in the Go project go through a few rounds of revision. This can be During May-July and Nov-Jan the Go project is in a code freeze, during which Please don’t reply on this GitHub thread. Visit golang.org/cl/350869. |
The current implementation of the log.Logger provides us with limited flexibility. With the new changes, it will provide more flexibility. The changes introduce new features such as Log Level, Formatter, Root Logger, Context support etc. but the changes made won't break any existing functionalities or affect any libraries which use log package. Thanks to the changes made, any custom logger implementation won't be needed and developer needs will be met. Instead, the formatter can be used to format the output. Fixes golang#13182
The current implementation of the log.Logger provides us with limited flexibility. With the new changes, it will provide more flexibility. The changes introduce new features such as Log Level, Formatter, Root Logger, Context support etc. but the changes made won't break any existing functionalities or affect any libraries which use log package. Thanks to the changes made, any custom logger implementation won't be needed and developer needs will be met. Instead, the formatter can be used to format the output. Fixes golang#13182
This PR (HEAD: c357000) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/go/+/350869 to see it. Tip: You can toggle comments from me using the |
The current implementation of the log.Logger provides us with limited flexibility. With the new changes, it will provide more flexibility. The changes introduce new features such as Log Level, Formatter, Root Logger, Context support etc. but the changes made won't break any existing functionalities or affect any libraries which use log package. Thanks to the changes made, any custom logger implementation won't be needed and developer needs will be met. Instead, the formatter can be used to format the output. Fixes golang#13182
This PR (HEAD: ffc9536) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/go/+/350869 to see it. Tip: You can toggle comments from me using the |
The current implementation of the log.Logger provides us with limited flexibility. With the new changes, it will provide more flexibility. The changes introduce new features such as Log Level, Formatter, Root Logger, Context support etc. but the changes made won't break any existing functionalities or affect any libraries which use log package. Thanks to the changes made, any custom logger implementation won't be needed and developer needs will be met. Instead, the formatter can be used to format the output. Fixes golang#13182
Message from Ian Lance Taylor: Patch Set 3: Code-Review-2 (1 comment) Please don’t reply on this GitHub thread. Visit golang.org/cl/350869. |
This PR (HEAD: 2fe9a32) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/go/+/350869 to see it. Tip: You can toggle comments from me using the |
The current implementation of the log.Logger provides us with limited flexibility. With the new changes, it will provide more flexibility. The changes introduce new features such as Log Level, Formatter, Root Logger, Context support etc. but the changes made won't break any existing functionalities or affect any libraries which use log package. Thanks to the changes made, any custom logger implementation won't be needed and developer needs will be met. Instead, the formatter can be used to format the output. Fixes golang#13182
The current implementation of the log.Logger provides us with
limited flexibility. With the new changes, it will provide more
flexibility. The changes introduce new features such as Log Level,
Formatter, Root Logger, Context support etc. but the changes made
won't break any existing functionalities or affect any libraries
which use log package. Thanks to the changes made, any custom logger
implementation won't be needed and developer needs will be met.
Instead, the formatter can be used to format the output.
Fixes #13182