-
Notifications
You must be signed in to change notification settings - Fork 413
we have to expect non-utf8 strings in tracing messages #770
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
Should the API here actually take |
makes sense. will update that |
ok that will break the api though, still ok? I doubt anyone is using that (but me^^) |
@alexcrichton in case API breakage is fine then the PR should be good to go |
3ddfd37
to
e770d52
Compare
If we do not want to break the API we would need a duplication of the API with the changed callback signature. let me know if you want that, then I update the PR |
@ehuss maybe you can chime in here? |
Hm right yeah that's true, let's keep the lossy string interpretation and this can be updated later during the next major version bump. |
e770d52
to
9cdc7af
Compare
This reverts commit 50a990f. # Conflicts: # src/tracing.rs
@alexcrichton done |
fixes #769