v2.0.10 regression ambiguous call; both system.==(x: T: tuple or object, y: T: tuple or object) ... and h.==(x: T: J, y: T: J) ... match for: (J, J)
#24231
Labels
Needs Backporting/Fixed in Devel
The issues can be solved via backporting
Description
h.nim
:Then:
Per https://nim-lang.org/docs/manual.html#overload-resolution documents neither of these are "exact" or "liiteral" matches, but the overload in
h.nim
is aso it at least isn't a worse match than
system.==(x: T: tuple or object, y: T: tuple or object)
, though it seems like by https://nim-lang.org/docs/manual.html#overload-resolution-first-trialcolon-catagory-matching [1] theobject
overload insystem
would be instead the next-lower-down category by subtypes, at least, that's the closest the manual gets to describing the situation precisely:But even if that's a tie, then https://nim-lang.org/docs/manual.html#overload-resolution-first-trialcolon-catagory-matching [2] would tip things to the
h.nim
generic overload.So according to any version either before or after precisely v2.0.10, and by the documentation, this should not be an ambiguous overload.
[1] "category"
[2] "trail" in body text?
Nim Version
Builds:
v2.0.8
:version-2-2
:devel
:Does not build:
Current Output
Expected Output
No response
Known Workarounds
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: