don't leak internal temporaries from dbg!#154994
Conversation
|
We discussed this today in the libs meeting. We agree that reverting is the safer option for 1.95, given the late timing. However, this PR might also miss the 1.96 branch if it's not merged quickly, and then we probably will want a backport there. So, we're going to leave the nomination for now and see where things stand next week. |
|
I've posted reverts in #154999 |
|
@bors r+ It feels like we really want some kind of general test and/or language construct that makes this much less of a pain to write, though I guess probably most ecosystem macros wouldn't hit the same set of wide users needing the particular incantation to be 'perfect'. |
…uwer Rollup of 6 pull requests Successful merges: - #155057 (Update libc to v0.2.184) - #154967 (Test(lib/sync): Fix `test_rwlock_max_readers` for x86 Win7) - #154994 (don't leak internal temporaries from `dbg!`) - #155130 (Stabilize feature `isolate_most_least_significant_one`) - #154925 (Make Box/Rc/Arc::into_array allocator-aware (and add doctest)) - #155063 (`ty::Alias`: replace `def_id: did` with `def_id`)
…uwer Rollup of 6 pull requests Successful merges: - #155057 (Update libc to v0.2.184) - #154967 (Test(lib/sync): Fix `test_rwlock_max_readers` for x86 Win7) - #154994 (don't leak internal temporaries from `dbg!`) - #155130 (Stabilize feature `isolate_most_least_significant_one`) - #154925 (Make Box/Rc/Arc::into_array allocator-aware (and add doctest)) - #155063 (`ty::Alias`: replace `def_id: did` with `def_id`)
Rollup merge of #154994 - dianne:no-dbg-temp, r=Mark-Simulacrum don't leak internal temporaries from `dbg!` Fixes #154988 r? @Mark-Simulacrum as the reviewer of #154074
|
Did this get merged in time for the 1.96.0 beta branch? (If not, we'll need to beta backport.) Edit: It did not. So, a beta backport to 1.96.0 is needed. |
Revert tearing changes to `dbg!` Since the primary change to `dbg!` in #149869, we've been chasing a few regressions: * #153850, fixed by #154074 * #154988, fixed by #154994 * #155902, proposed fix in #155915 We already reverted this once, on beta only to prevent these regressions from shipping in 1.95. In that most recent PR, we decided that it would be better to revert `dbg!` to its original state everywhere (`main` and 1.96-`beta`), and then we can consider it from scratch later. So here I've reverted the change and its fixes, but kept the regression tests, including the pending one. cc @joboet @dianne @rust-lang/libs @rustbot label beta-nominated
These are all tests from trying to fix the tear-free `dbg!`: * rust-lang#154074 * rust-lang#154994 * rust-lang#155915 These should also work as we revert to the old `dbg!`, so we should keep the tests to make sure they don't regress again. Co-authored-by: dianne <diannes.gm@gmail.com> (cherry picked from commit 6f35b83)
Revert tearing changes to `dbg!` Since the primary change to `dbg!` in rust-lang/rust#149869, we've been chasing a few regressions: * rust-lang/rust#153850, fixed by rust-lang/rust#154074 * rust-lang/rust#154988, fixed by rust-lang/rust#154994 * rust-lang/rust#155902, proposed fix in rust-lang/rust#155915 We already reverted this once, on beta only to prevent these regressions from shipping in 1.95. In that most recent PR, we decided that it would be better to revert `dbg!` to its original state everywhere (`main` and 1.96-`beta`), and then we can consider it from scratch later. So here I've reverted the change and its fixes, but kept the regression tests, including the pending one. cc @joboet @dianne @rust-lang/libs @rustbot label beta-nominated
Fixes #154988
r? @Mark-Simulacrum as the reviewer of #154074