[charliermarsh]

We coalesce adjacent string and version ranges after mapping their children. Boolean operations can make previously distinct children identical; retaining separate edges then interns two representations of the same marker, so marker equality depends on construction order.

For example, combining extra == 'test' with (platform_machine == 'aarch64' and extra == 'test') or platform_machine == 'x86_64' using OR produces the same function as platform_machine == 'x86_64' or extra == 'test'. Both trees already render that way, but they compare unequal because the first retains a redundant boundary at aarch64. We merge that boundary before interning the node, while retaining gaps in restricted ranges.

[codspeed]

Merging this PR will not alter performance

⚠️ 8 benchmarks spent significant time in system calls

System calls cannot be consistently instrumented, so they are not included in the measure, which understates the real cost. Please switch to the Walltime instrument to accurately measure system calls.

Measurement and system calls

• install_wheel_many_files
• unpack_sdist_many_files
• resolve_warm_airflow
• run_python_version_synthetic_workspace
• resolve_warm_jupyter
• resolve_warm_jupyter_universal
• discover_workspace_from_all_members_with_excludes
• discover_workspace_from_all_members

✅ 69 untouched benchmarks
⏩ 54 skipped benchmarks¹

---

_{Comparing charlie/marker-range-normalization (d09070b) with main (9db4e27)}

Footnotes

1. 54 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. ↩

[astral-sh-bot]

uv test inventory changes

This PR changes the tests when compared with the main base revision.

• Added tests: 2
• Removed tests: 0
• Changed suites: 1

uv-pep508: +2 / -0

Added:

• uv-pep508::marker::tree::test::coalesce_mapped_string_ranges
• uv-pep508::marker::tree::test::coalesce_mapped_version_ranges

Removed: none