Task: Fix nullable operator comparison on Atomic types #126
Labels
good first issue
Good for newcomers
pri:normal
up for grabs
This issue is open to be worked on by anyone
Milestone
The current operator comparison logic on Atomic types is broken in 3 ways:
GetValueOrDefault()
on nullable value types to do the comparison rather than properly checking fornull
input. We should only returntrue
if both sides arenull
if either of them are. But, we are normalizingnull
to be the same as 0, which is not correct.null
, so they could throw an NRE. We need to addnull
checking.See: apache/lucenenet#1064
The text was updated successfully, but these errors were encountered: