r? @oli-obk

(rust_highfive has picked a reviewer for you, use r? to override)

@bors try @rust-timer queue

Awaiting bors try build completion

@bors try

⌛ Trying commit 1a28bb0 with merge 49d7eb9f08603d5d5d3a7f1e34de7ab706096d3c...

☀️ Try build successful - checks-actions
Build commit: 49d7eb9f08603d5d5d3a7f1e34de7ab706096d3c (49d7eb9f08603d5d5d3a7f1e34de7ab706096d3c)

Queued 49d7eb9f08603d5d5d3a7f1e34de7ab706096d3c with parent 7bade6e, future comparison URL.

Finished benchmarking try commit (49d7eb9f08603d5d5d3a7f1e34de7ab706096d3c): comparison url.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying rollup- to bors.

Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up.

@bors rollup=never

Perf is basically neutral and this just increases complexity. I'm not sure the tradeoff is worth it.

It looks like a small improvement to me, but as @jackh726 mentioned it does worsen the experience of working on it in the future so I am going ahead and close this for now