-
Notifications
You must be signed in to change notification settings - Fork 67
having a single Buffer in LoggerSet for locking #197
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@ruicc Are you OK with this PR? |
I will check behaviours.. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checking code and behaviours finished. LGTM!
pushLog :: IORef FD -> Logger -> LogStr -> IO () | ||
pushLog fdref logger@(Logger size mbuf ref) nlogmsg@(LogStr nlen nbuilder) | ||
pushLog :: IORef FD -> BufSize -> MVar Buffer -> Logger -> LogStr -> IO () | ||
pushLog fdref size mbuf logger@(Logger ref) nlogmsg@(LogStr nlen nbuilder) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Writing is protected by the same MVar
when message size is longer than buffer size. OK.
Merged. |
3.1.1 * More time-ordered logging functions [#199](kazu-yamamoto/logger#199 3.1.0 * Having a single Buffer in LoggerSet for locking [#197](kazu-yamamoto/logger#197. This would have performance penalty. So, the major version bumps up. If you see performance regression, please register an issue on github.
This should fix #196