Use error!
/warn!
logs instead of println!
#84
Merged
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.
Writing to
stdout
will panic if the pipe is broken. This can happen, for example, if you run (in Linux):Then repeatedly hit
<Tab>
to make it printEvent bell([])
to the (already closed)STDOUT
. After a few tabs it'll crash - because it is trying to write to a broken pipe.The macros from the
log
crate don't crash when the pipe is broken. It also makes more sense to use them, since these prints are not the actual output of the application.