Remove the unused StrictComparison::to_compare_operator

[connortsui20]

Rationale for this change

Its last caller was the between_canonical fallback, which #9404 rewrote to build its operators with to_operator. Nothing else in the workspace calls it, and it is pub const fn, so no dead-code lint will report it later.

• Stacked on: fix: honor Kleene AND semantics for Between null bounds #9404

What changes are included in this PR?

Deletes the method and the CompareOperator import it needed. Split out from #9404 because StrictComparison is public and eight crates use it, so removing a method from it is a separate decision from a semantics fix.

What APIs are changed? Are there any user-facing changes?

StrictComparison::to_compare_operator is gone. No caller exists in the workspace, but it was reachable, so this is a public API removal. to_operator covers the same need and returns the Operator that callers actually want.

---

Generated by Claude Code

[codspeed-hq]

Merging this PR will degrade performance by 13.85%

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

❌ 2 regressed benchmarks
✅ 1992 untouched benchmarks
⏩ 89 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	cold_misaligned[(64, 256)]	4.4 ms	5.3 ms	-16.96%
❌	Simulation	compress_fsst[(1000, 64, 8)]	1 ms	1.2 ms	-10.63%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing ct/remove-to-compare-operator (41a7eaa) with claude/github-issue-9212-ia0abi (33cbc33)}

Footnotes

1. 89 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩