no need to check assertion on fast path as will always hold.

[gilescope]

V small change. Easy to review though!

[rust-highfive]

r? @dtolnay

(rust-highfive has picked a reviewer for you, use r? to override)

[lcnr]

r? @lcnr
after the perf run r=me

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

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

[bors]

⌛ Trying commit b70428b with merge ebeae584970a367c0e843b436291ca9c78ad69cb...

[bors]

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

[rust-timer]

Queued ebeae584970a367c0e843b436291ca9c78ad69cb with parent dd4851d, future comparison URL.

[rust-timer]

Finished benchmarking try commit (ebeae584970a367c0e843b436291ca9c78ad69cb): 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
@rustbot label: +S-waiting-on-review -S-waiting-on-perf

[lcnr]

mostly looks like noise

@bors r+

[bors]

📌 Commit b70428b has been approved by lcnr

[bors]

⌛ Testing commit b70428b with merge cd36bd46cc59a7dd156872eebf1ed652259b7c4c...

[bors]

💥 Test timed out

[rust-log-analyzer]

A job failed! Check out the build log: (web) (plain)

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

[lcnr]

@bors retry

[bors]

⌛ Testing commit b70428b with merge f1c47c7...

[bors]

☀️ Test successful - checks-actions
Approved by: lcnr
Pushing f1c47c7 to master...