Skip to content
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

we have to expect non-utf8 strings in tracing messages #770

Merged
merged 5 commits into from Nov 30, 2021

Conversation

extrawurst
Copy link
Contributor

fixes #769

@alexcrichton
Copy link
Member

Should the API here actually take &[u8] instead of &str to reflect how it's not always utf-8?

@extrawurst
Copy link
Contributor Author

makes sense. will update that

@extrawurst
Copy link
Contributor Author

extrawurst commented Nov 22, 2021

ok that will break the api though, still ok? I doubt anyone is using that (but me^^)

@extrawurst
Copy link
Contributor Author

@alexcrichton in case API breakage is fine then the PR should be good to go

@extrawurst
Copy link
Contributor Author

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

@extrawurst
Copy link
Contributor Author

@ehuss maybe you can chime in here?

@alexcrichton
Copy link
Member

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.

Stephan Dilly added 2 commits November 29, 2021 22:52
@extrawurst
Copy link
Contributor Author

@alexcrichton done

@alexcrichton alexcrichton merged commit 4979a86 into rust-lang:master Nov 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

panic in tracing
2 participants