Repository navigation
regression: temporary value dropped while borrowed #148974
Description
[INFO] [stdout] error[E0716]: temporary value dropped while borrowed
[INFO] [stdout] --> src/cmd/pretty_term.rs:81:46
[INFO] [stdout] |
[INFO] [stdout] 80 | / match (v.status().success(), v.status().code()) {
[INFO] [stdout] 81 | | (false, Some(c)) => &format!("({c}) "),
[INFO] [stdout] | | ^^^^^^^^^^^^^^^^-
[INFO] [stdout] | | | |
[INFO] [stdout] | | | temporary value is freed at the end of this statement
[INFO] [stdout] | | creates a temporary value which is freed while still in use
[INFO] [stdout] 82 | | _ => "",
[INFO] [stdout] 83 | | }
[INFO] [stdout] | |_____________________- borrow later used here
[INFO] [stdout] |
[INFO] [stdout] = note: consider using a `let` binding to create a longer lived value
[INFO] [stdout] = note: this error originates in the macro `format` (in Nightly builds, run with -Z macro-backtrace for more info)
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/3tothe6.u3/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/AnimalRacional.rust-mc-status-server/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/Koyin2005.Kay/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/LevitatingBusinessMan.notificationd/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/RileyLeff.pyst/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/TimL135.gtRust/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/Uzaaft.ratatosk/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/WhyNeet.BlastView/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/alessandrobologna.copilot-lmstudio-proxy/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/bartnv.rnr/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/chlaty.chlaty-hianime/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/chlaty.chlaty-lib-hydrahd/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/erikh.cupnp/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/eyemotif.eyebot2/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/kjuulh.noil/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/kkireeva98.gpu_scheduler_sim/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/mikemiller35.my_order_book/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/scritty1249.Sauron_POE2/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/theubusu.ptdump/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/yeizero.offline-judge-cli/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/gh/zyl-hub.sessio/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/reg/cupnp-0.1.1/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/reg/gradle-dependency-health-checker-0.4.1/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/reg/noil-0.1.2/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.92-3/beta-2025-11-01/reg/notificationd-0.6.0/log.txt
Activity
theemathas commentedon Nov 15, 2025
I haven't looked at the individual regressions, but this looks like the intended regression from #145838
See also #148427, which is related.
cc @dianne
dianne commentedon Nov 15, 2025
These are intended breakage from #145838, yeah. It's unfortunate how many more instances have popped up since the PR's crater run.
Mark-Simulacrum commentedon Nov 15, 2025
#145838 (comment) seems like the salient comment. The majority of these are github repositories, but it does seem like we at minimum will want to make sure to call this out in release notes (#146274 will take care of that).
theemathas commentedon Nov 16, 2025
Do we need to open issues/PRs on these repos?
apiraino commentedon Nov 27, 2025
Looking at past cases of incoming breaking changes, my understanding is that we don't need to do that and it is generally left to our contributors' deciding if they have time for opening issues or submitting patches in other projects.
wesleywiser commentedon Dec 11, 2025
Closing as intended changes from #145838