passing null to a method/constructor that has multiple signatures about ilspy HOT 4 CLOSED

This affects more than just 'null' - for example, take two method signatures (string, object) and (object, string), and a call ("Hello", "World") - the decompiler will have to detect that overload resolution would not produce the desired result, and then insert casts where necessary.

from ilspy.

A simple solution would be to use casts whenever there is more then one overload. Or whenever there is more then one one applicable overload. I would not go as far as implementing "betterness".

from ilspy.

NRefactory already implements applicability testing, "betterness" (see OverloadResolution.BetterFunctionMember) and reports ambiguities.
We just need to translate from the Cecil type system to the NRefactory type system and reuse that implementation.
NRefactory even implements type inference, so we can avoid explicitly specifying type arguments when it's not necessary.

from ilspy.

I've changed the AstMethodBodyBuilder.TransformCall method to cope with this issue. How do a send you the patch file?

Perhaps, I made the change at too low a level. I'll look at BetterFunctionMember.

from ilspy.