Revert "Rollup merge of #80637 - LingMan:filter, r=oli-obk"

[rylev]

Reverts #80637 to test for possible performance regressions.

In the latest perf triage, the rollup that the reverted PR was a part of featured a performance regression. We are testing whether the reverted PR was indeed (at least partially) responsible.

This reverts commit faf8bed, reversing
changes made to 1c6593c.

r? @ghost

cc @LingMan @oli-obk

[rylev]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

[bors]

⌛ Trying commit f1150ba with merge 875ad6e79a63f1e23b2e3fb22b22441e0a0b8384...

[bors]

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

[rust-timer]

Queued 875ad6e79a63f1e23b2e3fb22b22441e0a0b8384 with parent 68ec332, future comparison URL.

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

[rust-timer]

Finished benchmarking try commit (875ad6e79a63f1e23b2e3fb22b22441e0a0b8384): 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

[rylev]

This change did not affect performance. Closing.