-
Notifications
You must be signed in to change notification settings - Fork 60
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
[WIP] Logging and more #55
base: master
Are you sure you want to change the base?
Conversation
Now that I think of it, I didn't actually use the But it is possible to add a log method to the Should The current ("byte counting for progress") |
Thanks for your contribution @stbuehler ! before I review it, can you please add an example to the example directory, so I'll be able to run it? |
I'll try to come up with something simple. Just to clarify: only the last commit actually adds the logging; the others before can be reviewed without the logging example :) I also thought about using a similar patch without breaking the API. And then realized how broken the current implementation is:
This could probably be fixed by printing newlines in PB, and removing them in MultiBar - but is it worth it to fix this? |
… missing windows]
Hi, I just added a commit providing an example and added another fix to the list, and removed the I also worked on a branch which doesn't break the API, but is based on the same fixes (#57) as this one: https://github.com/stbuehler/rust-pbr/tree/logging-keep-api Basically the API changes could be done in a separate "next version" branch, or be dropped completely. |
As requested in #44.
I split it up into many single commit, some of them not breaking the API, not all of them needed for logging.
The
ProgressReceiver
part (and the final logging part) will break the API - maybe it would be better to have a separate "next" branch for those changes (I have some more ideas :D).Windows not supported yet - maybe someone working on windows can help out.