[Mono-bugs] [Bug 21647] Changed - Overload resolution problem with null.

[bugzilla-daemon@rocky.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by lupus@ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=21647

--- shadow/21647	Sat Mar  9 06:20:21 2002
+++ shadow/21647.tmp.30214	Mon Mar 11 09:28:23 2002
@@ -2,13 +2,13 @@
 Product: Mono/MCS
 Version: unspecified
 OS: other
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: Misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: lupus@ximian.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -26,7 +26,22 @@
 different with our corlib: on windows the right method happened to come
 first...).
 
 ------- Additional Comments From lupus@ximian.com  2002-03-09 06:20 -------
 Created an attachment (id=1505)
 Failing test case.
+
+
+------- Additional Comments From lupus@ximian.com  2002-03-11 09:28 -------
+It looks like ImplicitReferenceConversion() does a check from null to
+a reference type:
+
+if (expr is NullLiteral && !target_type.IsValueType)
+	return new EmptyCast (expr, target_type);
+
+and a comment indicates that the same checks should be done in 
+StandardConversionExists() (indeed there is a FIXME there related to
+this very issue). The problem is that to do the check an expression is
+needed, while StandardConversionExists() takes only types.
+
+Hope this helps.