Bug 7805 - Internal Compile Error when accidentally linking against not loadable assembly with implicit constructor
Summary: Internal Compile Error when accidentally linking against not loadable assembl...
Status: RESOLVED FIXED
Alias: None
Product: Compilers
Classification: Mono
Component: C# ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Marek Safar
URL:
Depends on:
Blocks:
 
Reported: 2012-10-11 16:36 UTC by Chris Hamons
Modified: 2012-10-12 03:26 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Chris Hamons 2012-10-11 16:36:29 UTC
I'm seeing this error:

Internal Compiler Error: Method not found: Class.op_Explicit CS0594

The example I'm running into has the following:

Assembly A:
   Call method that returns a Foo.

Assembly B:
   Foo is derived class of Type Bar
   Bar has an implicit constructor to type Buzz
   Buzz is defined in an assembly that doesn't load well against Mono (as opposed to the Mono friendly copy in another directory [our mistake]).

Relinking our reference to the version that has Buzz and is loadable makes it go away.

Yes, we shouldn't be adding references to assemblies that don't load under Mono, but the compiler should never ICE.

If you need a example, I can try to dig one up, but the only examples I have at hand involve assemblies I can't publicly post.
Comment 1 Marek Safar 2012-10-12 03:26:39 UTC
Closing as fixed as Mono 2.11 has new mechanism to check this sort of errors and will most likely fix yours as well.