[ubuntu-mono] [Bug 615112] Re: Compiler crashes with generic parameter arrays in constructors
Phill
615112 at bugs.launchpad.net
Mon Feb 14 16:00:29 UTC 2011
** Description changed:
Binary package hint: mono
If you have a class with a default constructor, a constructor that
accepts a parameter array of a generic type, and one that accepts a
parameter array of a non-generic type, and a call to the constructor
with no arguments then the compiler crashes.
If the default constructor did not exist this would create an ambiguity,
but the compiler also crashes rather than reporting this. MS compiles
the code and calls the parameter-less default constructor.
I've attached a code file that illustrates this problem, which requires
references to System and System.Core assemblies.
- The workaround is to replace the generic constructor to include on
+ The workaround is to replace the generic constructor to include one
mandatory element before the parameter array.
This bug appears to be unfixed even in the latest versions of mono.
--
You received this bug notification because you are a member of Ubuntu
CLI/Mono Uploaders, which is subscribed to mono in ubuntu.
https://bugs.launchpad.net/bugs/615112
Title:
Compiler crashes with generic parameter arrays in constructors
Status in “mono” package in Ubuntu:
New
Bug description:
Binary package hint: mono
If you have a class with a default constructor, a constructor that
accepts a parameter array of a generic type, and one that accepts a
parameter array of a non-generic type, and a call to the constructor
with no arguments then the compiler crashes.
If the default constructor did not exist this would create an
ambiguity, but the compiler also crashes rather than reporting this.
MS compiles the code and calls the parameter-less default constructor.
I've attached a code file that illustrates this problem, which
requires references to System and System.Core assemblies.
The workaround is to replace the generic constructor to include one
mandatory element before the parameter array.
This bug appears to be unfixed even in the latest versions of mono.
More information about the Ubuntu-mono
mailing list