Add a logging package. #43
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
See README.md for a detailed explanation. It's intended to replace the Go standard library's `log` package, which is IMHO very lacking compared to standard logging solutions in other languages.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an attempt to generalize and improve upon the
trace()mechanism currently used in theicepackage. It defines a leveled logging API, wherein each log statement is assigned a level (corresponding to importance or verbosity). Tags can be used to decide, at runtime, which log statements in each package actually get printed.I haven't profiled, so I don't know how performant this implementation is, but I believe it's decent. Log statements that are too verbose for the chosen log level are discarded at the earliest possible moment.
Log statements are printed to
stderrby default. They are colored according to a scheme that seemed reasonable to me, but there's currently no way to disable or modify the colored output. These are areas for improvement in the future.