[Mono-bugs] [Bug 44845][Wis] Changed - MCS doesn't find the best overloaded match for a constructor
Wed, 30 Jul 2003 13:20:42 -0400 (EDT)
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 email@example.com.
--- shadow/44845 Wed Jul 30 13:13:16 2003
+++ shadow/44845.tmp.19942 Wed Jul 30 13:20:42 2003
@@ -220,6 +220,16 @@
that didn't change the result.
------- Additional Comments From firstname.lastname@example.org 2003-07-30 13:13 -------
Am working on it - seems to me that the contructor from System.Object
is sneaking in and creating havoc in overload resolution.
+------- Additional Comments From email@example.com 2003-07-30 13:20 -------
+Okay I was blabbing before.
+It seems that the overload resolution process finds that none of the
+three applicable constructors match and that is what I find very strange.
+It seems to be related to the issue of the same type coming from
+different assemblies as Lupus pointed out. Is the type in corlib
+marked internal ?