-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Merge sys_common::bytestring
back into os_str_bytes
#85001
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
sys_common::bytestring
into os_str_bytes
sys_common::bytestring
back into os_str_bytes
☔ The latest upstream changes (presumably #84967) made this pull request unmergeable. Please resolve the merge conflicts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to me, thanks!
r? @JohnTitor @bors r+ |
📌 Commit 059008f has been approved by |
Rollup of 7 pull requests Successful merges: - rust-lang#84029 (add `track_path::path` fn for usage in `proc_macro`s) - rust-lang#85001 (Merge `sys_common::bytestring` back into `os_str_bytes`) - rust-lang#86308 (Docs: clarify that certain intrinsics are not unsafe) - rust-lang#86796 (Add a regression test for issue-70703) - rust-lang#86803 (Remove & from Command::args calls in documentation) - rust-lang#86807 (Fix double import in wasm thread ) - rust-lang#86813 (Add a help message to `unused_doc_comments` lint) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
bytestring
contains code for correctly debug formatting a byte slice ([u8]
). This functionality is and has historically only been used to provide the debug formatting of byte-based os-strings (on unix etc.).Having this functionality in the separate
bytestring
module was useful in the past to reduce duplication, as when it was addedos_str_bytes
was still split intosys::{unix, redox, wasi, etc.}::os_str
. However, now that is no longer the case, there is not much reason for thebytestring
functionality to be separate fromos_str_bytes
; I don't think it is very likely that another part of std will need to handle formatting byte strings that are not os-strings in the future (everything should beutf8
). This is why this PR merges the functionality ofbytestring
directly into the debug implementation inos_str_bytes
.