[DO NOT MERGE] Experiment with micro-optimizing push_str calls

[lolbinarycat]

No description provided.

[lolbinarycat]

@bors2 try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[lolbinarycat]

@bors try cancel

[rust-bors]

Try build cancelled. Cancelled workflows:

• https://github.com/rust-lang/rust/actions/runs/19147789788

[lolbinarycat]

@bors2 try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[lolbinarycat]

@bors try cancel

[rust-bors]

Try build cancelled. Cancelled workflows:

• https://github.com/rust-lang/rust/actions/runs/19148135975

[lolbinarycat]

@bors2 try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[Kobzol]

Btw, you don't need to cancel the previous try build when making a new one. Bors will automatically cancel the previous one.

[rust-log-analyzer]

The job aarch64-gnu-llvm-20-1 failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[RUSTC-TIMING] rustc_demangle test:false 1.214
error: missing documentation for a method
    --> library/alloc/src/string.rs:1117:5
     |
1117 |     pub fn push_str_slice(&mut self, slice: &[&str]) {
     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
     |
     = note: `-D missing-docs` implied by `-D warnings`
     = help: to override `-D warnings` add `#[allow(missing_docs)]`

[rust-bors]

☀️ Try build successful (CI)
Build commit: 978d49e (978d49ebec63bc482a297308eb28bd9bfff55fb6, parent: c90bcb9571b7aab0d8beaa2ce8a998ffaf079d38)

[rust-timer]

Queued 978d49e with parent c90bcb9, future comparison URL.
There are currently 2 preceding artifacts in the queue.
It will probably take at least ~3.3 hours until the benchmark run finishes.

[lolbinarycat]

Huh. CI failed but the try build didn't, is this another case of a check only being run in CI, or did something about bors change so that perf can continue even if there's an issue?