Allow storing `format_args!()` in a variable #140748

m-ou-se · 2025-05-07T16:01:52Z

Tracking issue for super let: #139076

Tracking issue for format_args: #99012

This change allows:

let name = "world";
let f = format_args!("hello {name}!"); // New: Store format_args!() for later!

println!("{f}");

This will need an FCP.

This implementation makes use of super let, which is unstable and might not exist in the future in its current form. However, it is entirely reasonable to assume future Rust will always have a way of expressing temporary lifetimes like this, since the (stable) pin!() macro needs this too. (This was also the motivation for merging #139114.)

(This is a second version of #139135)

m-ou-se · 2025-05-07T16:14:39Z

@bors try @rust-timer queue

bors · 2025-05-07T16:15:56Z

⌛ Trying commit d261de6 with merge beb8d4e...

Allow storing format_args!() in variable Fixes rust-lang#92698 Tracking issue for super let: rust-lang#139076 This change allows: ```rust let name = "world"; let f = format_args!("hello {name}!"); println!("{f}"); ``` This will need an FCP. This implementation makes use of `super let`, which is unstable and might not exist in the future in its current form. However, it is entirely reasonable to assume future Rust will always have _a_ way of expressing temporary lifetimes like this, since the (stable) `pin!()` macro needs this. (This was also the motivation for merging rust-lang#139114.) > [!NOTE] > This PR causes many subtle changes in diagnostics output. Most of those are good. Some of those are bad. I've collected all the bad ones in the last commit. Those still need fixing. Marking this PR as draft. (This is a second version of rust-lang#139135)

bors · 2025-05-07T18:25:44Z

☀️ Try build successful - checks-actions
Build commit: beb8d4e (beb8d4ea463c3ae10548aabc62ac2cff505be075)

rust-timer · 2025-05-07T20:03:49Z

Finished benchmarking commit (beb8d4e): comparison URL.

Overall result: ❌✅ regressions and improvements - please read the text below

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf.

Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

@bors rollup=never
@rustbot label: -S-waiting-on-perf +perf-regression

Instruction count

This is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.

	mean	range	count
Regressions ❌ (primary)	0.4%	[0.2%, 1.1%]	24
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-2.4%	[-4.5%, -0.2%]	2
Improvements ✅ (secondary)	-1.8%	[-1.9%, -1.7%]	6
All ❌✅ (primary)	0.2%	[-4.5%, 1.1%]	26

Max RSS (memory usage)

Results (primary 0.4%, secondary -0.2%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	1.7%	[0.4%, 12.3%]	27
Regressions ❌ (secondary)	3.8%	[3.8%, 3.8%]	1
Improvements ✅ (primary)	-2.2%	[-6.1%, -0.5%]	13
Improvements ✅ (secondary)	-2.3%	[-3.2%, -1.3%]	2
All ❌✅ (primary)	0.4%	[-6.1%, 12.3%]	40

Cycles

Results (primary 0.1%, secondary 2.4%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	0.7%	[0.4%, 2.0%]	14
Regressions ❌ (secondary)	2.4%	[2.4%, 2.4%]	1
Improvements ✅ (primary)	-2.6%	[-5.4%, -0.5%]	3
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.1%	[-5.4%, 2.0%]	17

Binary size

Results (primary 0.1%, secondary 0.1%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	0.1%	[0.0%, 0.8%]	87
Regressions ❌ (secondary)	0.1%	[0.0%, 0.2%]	15
Improvements ✅ (primary)	-0.1%	[-0.4%, -0.0%]	6
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.1%	[-0.4%, 0.8%]	93

Bootstrap: 770.356s -> 770.437s (0.01%)
Artifact size: 365.20 MiB -> 365.11 MiB (-0.02%)

This message is no longer generated. This is probably a good thing. The relevant span is entirely in user code, and "format_args_nl" is an implementation detail with a name that isn't even public.

Diagnostics should know that the `&` for arguments in format_args!() come from the macro expansion rather than from the original source.

compiler/rustc_ast_lowering/src/format.rs

tests/ui/borrowck/issue-114374-invalid-help-fmt-args.stderr

jdonszelmann · 2025-06-19T13:28:41Z

bors · 2025-06-19T13:28:44Z

📌 Commit b4f2cac has been approved by jdonszelmann

It is now in the queue for this repository.

bors · 2025-06-19T19:13:36Z

⌛ Testing commit b4f2cac with merge 255aa22...

bors · 2025-06-19T22:18:07Z

☀️ Test successful - checks-actions
Approved by: jdonszelmann
Pushing 255aa22 to master...

github-actions · 2025-06-19T22:21:21Z

What is this?

This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 8de4c72 (parent) -> 255aa22 (this PR)

Test differences

Show 8 test diffs

Stage 1

[ui] tests/ui/borrowck/issue-114374-invalid-help-fmt-args.rs: pass -> [missing] (J1)
fmt::test_lifetime: [missing] -> pass (J2)

Stage 2

[ui] tests/ui/borrowck/issue-114374-invalid-help-fmt-args.rs: pass -> [missing] (J0)

Additionally, 5 doctest diffs were found. These are ignored, as they are noisy.

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 255aa220821c05c3eac7605fce4ea1c9ab2cbdb4 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

dist-aarch64-msvc: 14983.1s -> 8413.0s (-43.9%)
dist-aarch64-apple: 6723.7s -> 4689.2s (-30.3%)
x86_64-apple-2: 4537.4s -> 3543.9s (-21.9%)
dist-x86_64-apple: 11510.2s -> 9048.3s (-21.4%)
x86_64-apple-1: 7805.5s -> 6181.5s (-20.8%)
dist-apple-various: 8283.5s -> 6874.9s (-17.0%)
x86_64-gnu-llvm-19-2: 5280.0s -> 5852.9s (10.9%)
x86_64-gnu-aux: 5956.6s -> 6537.8s (9.8%)
mingw-check-tidy: 70.4s -> 77.1s (9.6%)
dist-various-2: 3377.5s -> 3110.7s (-7.9%)

How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

rust-timer · 2025-06-20T00:48:00Z

Finished benchmarking commit (255aa22): comparison URL.

Overall result: ❌✅ regressions and improvements - please read the text below

Our benchmarks found a performance regression caused by this PR.
This might be an actual regression, but it can also be just noise.

Next Steps:

If the regression was expected or you think it can be justified,
please write a comment with sufficient written justification, and add
@rustbot label: +perf-regression-triaged to it, to mark the regression as triaged.
If you think that you know of a way to resolve the regression, try to create
a new PR with a fix for the regression.
If you do not understand the regression or you think that it is just noise,
you can ask the @rust-lang/wg-compiler-performance working group for help (members of this group
were already notified of this PR).

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

	mean	range	count
Regressions ❌ (primary)	0.4%	[0.2%, 1.0%]	24
Regressions ❌ (secondary)	1.6%	[0.3%, 4.7%]	12
Improvements ✅ (primary)	-3.7%	[-7.1%, -0.3%]	2
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.1%	[-7.1%, 1.0%]	26

Max RSS (memory usage)

Results (primary 1.0%, secondary 2.3%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	3.0%	[2.1%, 4.3%]	4
Regressions ❌ (secondary)	3.8%	[2.6%, 6.5%]	4
Improvements ✅ (primary)	-3.2%	[-3.2%, -3.1%]	2
Improvements ✅ (secondary)	-3.7%	[-3.7%, -3.7%]	1
All ❌✅ (primary)	1.0%	[-3.2%, 4.3%]	6

Cycles

Results (primary -6.8%, secondary 5.1%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	5.1%	[4.0%, 7.2%]	4
Improvements ✅ (primary)	-6.8%	[-6.8%, -6.8%]	1
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-6.8%	[-6.8%, -6.8%]	1

Binary size

Results (primary 0.1%, secondary 1.9%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	0.2%	[0.0%, 0.7%]	60
Regressions ❌ (secondary)	1.9%	[0.0%, 17.0%]	35
Improvements ✅ (primary)	-0.1%	[-0.2%, -0.0%]	5
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.1%	[-0.2%, 0.7%]	65

Bootstrap: 691.904s -> 692.261s (0.05%)
Artifact size: 372.02 MiB -> 371.96 MiB (-0.02%)

Kobzol · 2025-06-20T04:55:27Z

Weird, somehow this makes binary size and linking time of workspaces with a lot of crates much worse.

rylev · 2025-06-24T11:36:20Z

@m-ou-se the perf regression here seems legitimate. I tried to look into why, but I couldn't really tell. Any thoughts on the performance impact here?

…elmann Allow storing `format_args!()` in variable Fixes rust-lang#92698 Tracking issue for super let: rust-lang#139076 Tracking issue for format_args: rust-lang#99012 This change allows: ```rust let name = "world"; let f = format_args!("hello {name}!"); // New: Store format_args!() for later! println!("{f}"); ``` This will need an FCP. This implementation makes use of `super let`, which is unstable and might not exist in the future in its current form. However, it is entirely reasonable to assume future Rust will always have _a_ way of expressing temporary lifetimes like this, since the (stable) `pin!()` macro needs this too. (This was also the motivation for merging rust-lang#139114.) (This is a second version of rust-lang#139135)

Pkgsrc changes: * Adjust patches to adapt to upstream changes and new versions. * assosicated checksums Upstream changes relative to 1.88.0: Version 1.89.0 (2025-08-07) ========================== Language -------- - [Stabilize explicitly inferred const arguments (`feature(generic_arg_infer)`)] (rust-lang/rust#141610) - [Add a warn-by-default `mismatched_lifetime_syntaxes` lint.] (rust-lang/rust#138677) This lint detects when the same lifetime is referred to by different syntax categories between function arguments and return values, which can be confusing to read, especially in unsafe code. This lint supersedes the warn-by-default `elided_named_lifetimes` lint. - [Expand `unpredictable_function_pointer_comparisons` to also lint on function pointer comparisons in external macros] (rust-lang/rust#134536) - [Make the `dangerous_implicit_autorefs` lint deny-by-default] (rust-lang/rust#141661) - [Stabilize the avx512 target features] (rust-lang/rust#138940) - [Stabilize `kl` and `widekl` target features for x86] (rust-lang/rust#140766) - [Stabilize `sha512`, `sm3` and `sm4` target features for x86] (rust-lang/rust#140767) - [Stabilize LoongArch target features `f`, `d`, `frecipe`, `lasx`, `lbt`, `lsx`, and `lvz`] (rust-lang/rust#135015) - [Remove `i128` and `u128` from `improper_ctypes_definitions`] (rust-lang/rust#137306) - [Stabilize `repr128` (`#[repr(u128)]`, `#[repr(i128)]`)] (rust-lang/rust#138285) - [Allow `#![doc(test(attr(..)))]` everywhere] (rust-lang/rust#140560) - [Extend temporary lifetime extension to also go through tuple struct and tuple variant constructors] (rust-lang/rust#140593) Compiler -------- - [Default to non-leaf frame pointers on aarch64-linux] (rust-lang/rust#140832) - [Enable non-leaf frame pointers for Arm64EC Windows] (rust-lang/rust#140862) - [Set Apple frame pointers by architecture] (rust-lang/rust#141797) Platform Support ---------------- - [Add new Tier-3 targets `loongarch32-unknown-none` and `loongarch32-unknown-none-softfloat`] (rust-lang/rust#142053) Refer to Rust's [platform support page][platform-support-doc] for more information on Rust's tiered platform support. [platform-support-doc]: https://doc.rust-lang.org/rustc/platform-support.html Libraries --------- - [Specify the base path for `file!`] (rust-lang/rust#134442) - [Allow storing `format_args!()` in a variable] (rust-lang/rust#140748) - [Add `#[must_use]` to `[T; N]::map`] (rust-lang/rust#140957) - [Implement `DerefMut` for `Lazy{Cell,Lock}`] (rust-lang/rust#129334) - [Implement `Default` for `array::IntoIter`] (rust-lang/rust#141574) - [Implement `Clone` for `slice::ChunkBy`] (rust-lang/rust#138016) - [Implement `io::Seek` for `io::Take`] (rust-lang/rust#138023) Stabilized APIs --------------- - [`NonZero<char>`] (https://doc.rust-lang.org/stable/std/num/struct.NonZero.html) - Many intrinsics for x86, not enumerated here - [AVX512 intrinsics](rust-lang/rust#111137) - [`SHA512`, `SM3` and `SM4` intrinsics] (rust-lang/rust#126624) - [`File::lock`] (https://doc.rust-lang.org/stable/std/fs/struct.File.html#method.lock) - [`File::lock_shared`] (https://doc.rust-lang.org/stable/std/fs/struct.File.html#method.lock_shared) - [`File::try_lock`] (https://doc.rust-lang.org/stable/std/fs/struct.File.html#method.try_lock) - [`File::try_lock_shared`] (https://doc.rust-lang.org/stable/std/fs/struct.File.html#method.try_lock_shared) - [`File::unlock`] (https://doc.rust-lang.org/stable/std/fs/struct.File.html#method.unlock) - [`NonNull::from_ref`] (https://doc.rust-lang.org/stable/std/ptr/struct.NonNull.html#method.from_ref) - [`NonNull::from_mut`] (https://doc.rust-lang.org/stable/std/ptr/struct.NonNull.html#method.from_mut) - [`NonNull::without_provenance`] (https://doc.rust-lang.org/stable/std/ptr/struct.NonNull.html#method.without_provenance) - [`NonNull::with_exposed_provenance`] (https://doc.rust-lang.org/stable/std/ptr/struct.NonNull.html#method.with_exposed_provenance) - [`NonNull::expose_provenance`] (https://doc.rust-lang.org/stable/std/ptr/struct.NonNull.html#method.expose_provenance) - [`OsString::leak`] (https://doc.rust-lang.org/stable/std/ffi/struct.OsString.html#method.leak) - [`PathBuf::leak`] (https://doc.rust-lang.org/stable/std/path/struct.PathBuf.html#method.leak) - [`Result::flatten`] (https://doc.rust-lang.org/stable/std/result/enum.Result.html#method.flatten) - [`std::os::linux::net::TcpStreamExt::quickack`] (https://doc.rust-lang.org/stable/std/os/linux/net/trait.TcpStreamExt.html#tymethod.quickack) - [`std::os::linux::net::TcpStreamExt::set_quickack`] (https://doc.rust-lang.org/stable/std/os/linux/net/trait.TcpStreamExt.html#tymethod.set_quickack) These previously stable APIs are now stable in const contexts: - [`<[T; N]>::as_mut_slice`] (https://doc.rust-lang.org/stable/std/primitive.array.html#method.as_mut_slice) - [`<[u8]>::eq_ignore_ascii_case`] (https://doc.rust-lang.org/stable/std/primitive.slice.html#impl-%5Bu8%5D/method.eq_ignore_ascii_case) - [`str::eq_ignore_ascii_case`] (https://doc.rust-lang.org/stable/std/primitive.str.html#impl-str/method.eq_ignore_ascii_case) Cargo ----- - [`cargo fix` and `cargo clippy --fix` now default to the same Cargo target selection as other build commands.] (rust-lang/cargo#15192) Previously it would apply to all targets (like binaries, examples, tests, etc.). The `--edition` flag still applies to all targets. - [Stabilize doctest-xcompile.] (rust-lang/cargo#15462) Doctests are now tested when cross-compiling. Just like other tests, it will use the [`runner` setting] (https://doc.rust-lang.org/cargo/reference/config.html#targettriplerunner) to run the tests. If you need to disable tests for a target, you can use the [ignore doctest attribute] (https://doc.rust-lang.org/rustdoc/write-documentation/documentation-tests.html#ignoring-targets) to specify the targets to ignore. Rustdoc ----- - [On mobile, make the sidebar full width and linewrap] (rust-lang/rust#139831). This makes long section and item names much easier to deal with on mobile. Compatibility Notes ------------------- - [Make `missing_fragment_specifier` an unconditional error] (rust-lang/rust#128425) - [Enabling the `neon` target feature on `aarch64-unknown-none-softfloat` causes a warning] (rust-lang/rust#135160) because mixing code with and without that target feature is not properly supported by LLVM - [Sized Hierarchy: Part I](rust-lang/rust#137944) - Introduces a small breaking change affecting `?Sized` bounds on impls on recursive types which contain associated type projections. It is not expected to affect any existing published crates. Can be fixed by refactoring the involved types or opting into the `sized_hierarchy` unstable feature. See the [FCP report] (rust-lang/rust#137944 (comment)) for a code example. - The warn-by-default `elided_named_lifetimes` lint is [superseded by the warn-by-default `mismatched_lifetime_syntaxes` lint.] (rust-lang/rust#138677) - [Error on recursive opaque types earlier in the type checker] (rust-lang/rust#139419) - [Type inference side effects from requiring element types of array repeat expressions are `Copy` are now only available at the end of type checking] (rust-lang/rust#139635) - [The deprecated accidentally-stable `std::intrinsics::{copy,copy_nonoverlapping,write_bytes}` are now proper intrinsics] (rust-lang/rust#139916). There are no debug assertions guarding against UB, and they cannot be coerced to function pointers. - [Remove long-deprecated `std::intrinsics::drop_in_place`] (rust-lang/rust#140151) - [Make well-formedness predicates no longer coinductive] (rust-lang/rust#140208) - [Remove hack when checking impl method compatibility] (rust-lang/rust#140557) - [Remove unnecessary type inference due to built-in trait object impls] (rust-lang/rust#141352) - [Lint against "stdcall", "fastcall", and "cdecl" on non-x86-32 targets] (rust-lang/rust#141435) - [Future incompatibility warnings relating to the never type (`!`) are now reported in dependencies] (rust-lang/rust#141937) - [Ensure `std::ptr::copy_*` intrinsics also perform the static self-init checks] (rust-lang/rust#142575) Internal Changes ---------------- These changes do not affect any public interfaces of Rust, but they represent significant improvements to the performance or internals of rustc and related tools. - [Correctly un-remap compiler sources paths with the `rustc-dev` component] (rust-lang/rust#142377)

m-ou-se added T-lang Relevant to the language team T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. needs-fcp This change is insta-stable, or significant enough to need a team FCP to proceed. A-fmt Area: `core::fmt` labels May 7, 2025

m-ou-se removed T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver) A-tidy Area: The tidy tool labels May 7, 2025

This was referenced May 7, 2025

Allow storing format_args!() in variable or const #139135

Closed

Allow storing format_args! in a let binding #92698

Closed

m-ou-se force-pushed the super-format-args3 branch from 4971602 to d261de6 Compare May 7, 2025 16:08

rustbot added A-tidy Area: The tidy tool T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver) labels May 7, 2025

m-ou-se removed T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver) A-tidy Area: The tidy tool labels May 7, 2025

This comment has been minimized.

Sign in to view

rustbot added the S-waiting-on-perf Status: Waiting on a perf run to be completed. label May 7, 2025

This comment has been minimized.

Sign in to view

rustbot added the perf-regression Performance regression. label May 7, 2025

m-ou-se added 5 commits June 18, 2025 10:20

Remove 'this error originates in format_args_nl' from test output.

f608da2

This message is no longer generated. This is probably a good thing. The relevant span is entirely in user code, and "format_args_nl" is an implementation detail with a name that isn't even public.

Update unpretty tests.

58a5ab5

Fix span of AddrOf in format_args!() expansion.

42fc5ae

Diagnostics should know that the `&` for arguments in format_args!() come from the macro expansion rather than from the original source.

Bless/update tests.

a693c52

Update/bless clippy tests.

2c175e1

m-ou-se force-pushed the super-format-args3 branch from ae3bfda to 2c175e1 Compare June 18, 2025 08:32

jdonszelmann reviewed Jun 19, 2025

View reviewed changes

compiler/rustc_ast_lowering/src/format.rs Show resolved Hide resolved

compiler/rustc_ast_lowering/src/format.rs Outdated Show resolved Hide resolved

tests/ui/borrowck/issue-114374-invalid-help-fmt-args.stderr Show resolved Hide resolved

m-ou-se added 2 commits June 19, 2025 14:08

Use expr_ref.

2da3a66

Remove old format_args diagnostic.

b4f2cac

bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jun 19, 2025

bors added the merged-by-bors This PR was explicitly merged by bors. label Jun 19, 2025

bors merged commit 255aa22 into rust-lang:master Jun 19, 2025
11 checks passed

rustbot added this to the 1.89.0 milestone Jun 19, 2025

m-ou-se deleted the super-format-args3 branch June 20, 2025 06:04

Veykril mentioned this pull request Jun 20, 2025

println! macro is unsafe rust-lang/rust-analyzer#20051

Closed

apiraino removed the to-announce Announce this issue on triage meeting label Jun 26, 2025

tgross35 changed the title ~~Allow storing format_args!() in variable~~ Allow storing format_args!() in a variable Jul 3, 2025

cuviper mentioned this pull request Jul 17, 2025

Draft release notes for 1.89.0 #144097

Closed

Allow storing format_args!() in a variable #140748

Allow storing format_args!() in a variable #140748

Uh oh!

Conversation

m-ou-se commented May 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

m-ou-se commented May 7, 2025

Uh oh!

This comment has been minimized.

bors commented May 7, 2025

Uh oh!

This comment has been minimized.

bors commented May 7, 2025

Uh oh!

This comment has been minimized.

rust-timer commented May 7, 2025

Overall result: ❌✅ regressions and improvements - please read the text below

Uh oh!

Uh oh!

Uh oh!

Uh oh!

jdonszelmann commented Jun 19, 2025

Uh oh!

bors commented Jun 19, 2025

Uh oh!

bors commented Jun 19, 2025

Uh oh!

bors commented Jun 19, 2025

Uh oh!

Uh oh!

github-actions bot commented Jun 19, 2025

Test differences

Stage 1

Stage 2

Job duration changes

Uh oh!

rust-timer commented Jun 20, 2025

Overall result: ❌✅ regressions and improvements - please read the text below

Uh oh!

Kobzol commented Jun 20, 2025

Uh oh!

rylev commented Jun 24, 2025

Uh oh!

Uh oh!

Allow storing `format_args!()` in a variable #140748

Allow storing `format_args!()` in a variable #140748

m-ou-se commented May 7, 2025 •

edited

Loading