空传播运算符和Newtonsoft.Json 10.0.3异常

Question

I have installed "Newtonsoft.Json" version="10.0.3"

and there are two methods:

    public static bool IsNull_yes(dynamic source)
    {
        if (source.x == null || source.x.y == null) return true;
        return false;
    }

    public static bool IsNull_exception(dynamic source)
    {
        if (source.x?.y == null) return true;
        return false;
    }

Then I have program:

        var o = JObject.Parse(@"{  'x': null }");

        if (IsNull_yes(o) && IsNull_exception(o)) Console.WriteLine("OK");

        Console.ReadLine();

• When program calls IsNull_yes method then result is "true"
• When program calls IsNull_exception then result is exception: Microsoft.CSharp.RuntimeBinder.RuntimeBinderException: ''Newtonsoft.Json.Linq.JValue' does not contain a definition for 'y''

Is it Newtonsoft.Json or other bug?

Answer 1

The short answer is that source.x is 'sort of' null.

To see this, change the code as following:

public static bool IsNull_exception(dynamic source)
{
    var h = source.x;  
    Console.WriteLine(object.ReferenceEquals(null, h));   // false
    Console.WriteLine(null == h);                         // false  
    Console.WriteLine(object.Equals(h, null));            // false
    Console.WriteLine(h == null);                         // true

    if (source.x?.y == null) return true;
    return false;
}

You will note that false is written three times, then true . As such, the equality comparison used by dynamic is not the same as that used by object.Equals etc. See @dbc's awesome post for more details.

Unfortunately, since it is not really equal, null propagation doesn't kick in (since null propagation does not use the h == null style comparison).

As such the equivalent IsNull_yes implementation is not your existing code - but something closer to:

public static bool IsNull_yes(dynamic source)
{
    if (null == source.x || source.x.y == null) return true;
    return false;
}

which acts exactly the same way (ie throws an exception).

Answer 2

my guess is compiler must be checking if source.x?.y is still valid by looking at json string @"{ 'x': null }" . As compiler has to verify if y exists in case 'x' is really valid non-null reference, it throws RuntimeBinderException.