-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Change in behavior of debug format of strings containing \0
#95732
Comments
I see #95345 now. Context: this real-world test: https://github.com/influxdata/influxdb_iox/blob/c244b0328125b3fd1773b58d4e1b1aaf47c83fd3/logfmt/src/lib.rs#L387 I see this has caused some churn in ripgrep too, up to you all if this change is worth the churn. |
\0
This change was intentional. Indeed all debug formattings are always subject to change.
I'm not sure what this refers to — the ripgrep master branch has had no new commits since when this change landed in nightly, no PRs have been opened on ripgrep either, and no relevant-looking issues have been opened as far as I can tell. Ripgrep has been using the |
For anyone else who's curious (I'm not trying to relitigate this issue or anything), the ripgrep churn I was referring to was https://github.com/BurntSushi/ripgrep/pull/1722/files#diff-4dda3b4b1094bbd540a7548319bd9b4367e93ce4662873d863c219b1b0799adbL43 that I found through this comment. |
This follows this PR in rustc: <rust-lang/rust#95345> Which breakage was discussed here: <rust-lang/rust#95732> Because this landed in 1.61.0, the MSRV has to be updated accordingly.
This follows this PR in rustc: <rust-lang/rust#95345> Which breakage was discussed here: <rust-lang/rust#95732> Still relying on \0 would require bumping the MSRV to 1.61.0
This follows this PR in rustc: <rust-lang/rust#95345> Which breakage was discussed here: <rust-lang/rust#95732> Still relying on \0 would require bumping the MSRV to 1.61.0
I understand debug formatting is generally unstable, but wanted to raise this to make sure the change was intentional.
Code
I tried this test:
This test passes with stable Rust 1.60.0 (7737e0b 2022-04-04) (the release candidate that's going to be released tomorrow)
I expected this test to continue passing with 1.61.0-beta.1
Instead, I get this failure:
Version it worked on
It most recently worked on: stable release candidate 1.60.0 (7737e0b 2022-04-04)
Version with regression
rustc --version --verbose
:@rustbot modify labels: +regression-from-stable-to-beta -regression-untriaged
The text was updated successfully, but these errors were encountered: