-
Notifications
You must be signed in to change notification settings - Fork 244
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
logging without newline #533
Comments
I don't think the |
When I put |
You are using some specific logging implementation that is deciding to put a newline between them. This crate doesn't have any control over that. |
Well, I guess u mean flexi_logger. |
ur right. I guess |
No it doesn't. The |
No, it doesn't and that's why rust introduces |
Even if it's not baked into the EDIT: looking through the crate code and familiarizing myself with |
The concept of building up an event over an operation and emitting in a single blob at the end is sometimes called a "wide event". You can also do it using tracing, where multiple events are emitted within a single span. It is an interesting concept, but not one that I think exists at the level of abstraction this crate is concerned with. An implementation of I'll go ahead and close this one as the specific issue isn't related to |
Bumps [mimalloc](https://github.com/purpleprotocol/mimalloc_rust) from 0.1.31 to 0.1.32. - [Release notes](https://github.com/purpleprotocol/mimalloc_rust/releases) - [Commits](purpleprotocol/mimalloc_rust@v0.1.31...v0.1.32) --- updated-dependencies: - dependency-name: mimalloc dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Hello folks,
is it possible that I put a logline without a implicit newline at the end of the line? the macro log::info!() puts always a new line at the end.
It would be nice if I had the possibility to distinguish it like the print! or println! macro it does!!!!
The text was updated successfully, but these errors were encountered: