Repository navigation
10.x: RangeSetContains.Equivalent hands any other one-argument Contains to the value overload (port of #320) #326
Description
Problem
The same latent fallback as #320, in the copy of RangeSetContains.Equivalent that 10.1.0 ships for #288. Any one-argument Contains on RangeSet that is not the set type or IRange<> is sent to the value overload, so an overload added later would throw ArgumentException from the interceptor at query compile, without naming the missing arm.
Change
Cherry-pick the #320 fix with -x, together with its reflection test over every Contains overload.
Release
Internal, and no answer changes.
Activity
RangeSetContains.Equivalenthands any other one-argumentContainsonRangeSetto the value overload #320CaffeinatedCoder commentedon Oct 25, 2026
Scheduled for 10.3.0 (#408), 2026-10-25. The cherry-pick follows #320 once that is on
main(linked as blocked by #320). Re-checked 2026-10-25:Equivalentonrelease/10.xstill sends any other one-argumentContainstoValueMethod(RangeSetContains.cs:55-69).CaffeinatedCoder commentedon Oct 25, 2026
The #320 fix throws
MissingArm, which #295 added onmain. Onrelease/10.xthat arrives with #433, the port of #295, so this cherry-pick follows it (now linked as blocked by #433).CaffeinatedCoder commentedon Oct 25, 2026
PR #436, stacked on #435 (the port of #295).
fix: RangeSetContains.Equivalent refuses a Contains overload it has n…
Merge pull request #436 from CaffeinatedCoder/chore/326-rangeset-cont…
CaffeinatedCoder commentedon Oct 25, 2026
Fixed on
release/10.xby PR #436 (merged as 2dfa587).RangeSetContains.Equivalentmatches eachContainsoverload by its operand type on this line too, and refuses any other withMissingArm. Closed by hand, becauseCloses #nacts only onmain.