fix: string-left relational operator binding for custom types - #376
Merged
davideicardi merged 6 commits intoAug 20, 2026
Merged
Conversation
generalize default expressions for generic methods
davideicardi
approved these changes
Jun 4, 2026
davideicardi
changed the title
This was referenced Aug 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes string-left relational operator binding for custom types, e.g. "10" < m, "10" <= m, "10" > m, and "10" >= m.
Root cause
Relational operators special-cased any comparison with a string left operand and routed it through string.Compare. For string vs custom type, no matching string.Compare(string, T) exists, so a null MethodInfo was passed to Expression.Call, causing ArgumentNullException.
Fix
• Use the string.Compare shortcut only for string/string comparisons.
• Let string/custom relationals use normal binary operator resolution.
• Add fallback binding through a single implicit conversion when no direct user-defined operator matches.
Tests
Added NUnit coverage for all four relational operators in both operand orders, including direct string/custom operators, implicit-conversion fallback, and equality regressions.