Should Value.Equal() treat NaNs as non-equal to themselves?

[mordae]

Hi, I have encountered a situation. I have been using Value.Equal() to compare old and new revision of data to determine whether to push out an update notification and observed all updates result in a push. Apparently Value.Equal() treats two NaNs as unequal to each other, which kind of makes sense, but is also kind of impractical. What is your opinion?

By the way, this behavior also affects Value.Diff(), which issues updates such as these despite the value being NaN in both old and new version:

{ type: 'update', path: '/85/ackTime', value: NaN },

And while Value.Diff() does not promise that the changes it will produce are minimal, this is at least unexpected and possibly should be clearly documented.

Funnily enough, in Node:

> util.isDeepStrictEqual(Number.NaN, Number.NaN)
true

> Object.is(Number.NaN, Number.NaN)
true

> Number.NaN === Number.NaN
false