Rollup of 5 pull requests

[matthiaskrgr]

Successful merges:

• Implement TryFrom<&'_ mut [T]> for [T; N] #91086 (Implement TryFrom<&'_ mut [T]> for [T; N])
• Stabilize ControlFlow::{is_break, is_continue} #91091 (Stabilize ControlFlow::{is_break, is_continue})
• BTree: improve public descriptions and comments #91749 (BTree: improve public descriptions and comments)
• rustbot: Add autolabeling for T-compiler #91819 (rustbot: Add autolabeling for T-compiler)
• Make (*mut T)::write_bytes const #91824 (Make (*mut T)::write_bytes const)

Failed merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

[matthiaskrgr]

@bors r+ rollup=never p=5

[bors]

📌 Commit 9e662d0 has been approved by matthiaskrgr

[bors]

⌛ Testing commit 9e662d0 with merge f7fd79a...

[bors]

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing f7fd79a to master...

[rust-timer]

Finished benchmarking commit (f7fd79a): comparison url.

Summary: This change led to large relevant regressions 😿 in compiler performance.

• Large regression in instruction counts (up to 4.0% on incr-unchanged builds of deep-vector)

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please open an issue or create a new PR that fixes the regressions, add a comment linking to the newly created issue or PR, and then add the perf-regression-triaged label to this PR.

@rustbot label: +perf-regression