[Mono-bugs] [Bug 75773][Nor] New - [GMCS] runtime fails on a specific chain of generic method calls

[bugzilla-daemon at bugzilla.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 nazgul at omega.pl.

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

--- shadow/75773	2005-08-10 14:13:33.000000000 -0400
+++ shadow/75773.tmp.9302	2005-08-10 14:13:33.000000000 -0400
@@ -0,0 +1,78 @@
+Bug#: 75773
+Product: Mono: Runtime
+Version: 1.0
+OS: 
+OS Details: mono svn
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: nazgul at omega.pl               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: [GMCS] runtime fails on a specific chain of generic method calls
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+I got an assertion from runtime on specific pattern of generic methods
+calls. It is occuring also in Nemerle generated code, so it seems to be a
+runtime bug.
+
+Steps to reproduce the problem:
+1. Compile and run
+
+public class Map <b>
+{
+     b x;
+
+    public a Fold1 <a> (a ini)
+    {
+      return ini;
+    } 
+
+    public c Fold<c> (c ini)
+    {
+       Fold1 <b> (x);
+       return   ini;
+    }
+}
+
+
+public class LocalContext
+{
+    Map <string> locals = new Map <string> ();
+
+    public a Fold <a> (a acc)
+    {
+      return locals.Fold (acc);
+    }
+}
+
+class M {
+  static void Main () {
+     LocalContext x = new LocalContext ();
+     x.Fold ("a" );
+  }
+}
+
+Actual Results:
+** ERROR **: file metadata.c: line 1827
+(mono_metadata_parse_generic_param): assertion failed: (generic_container
+&& !generic_container->is_method)
+aborting...
+
+
+Expected Results:
+clear run
+
+How often does this happen? 
+Always
+
+Additional Information:
+This pattern occurs only once in our codebase, so we can easily create an
+workaround. But it would be nice to have it fixed :-)