GENERIC:invocation of operators on type parameter failed to compile

Igor Peshansky added a comment - 09/Mar/11 12:05 AM Two problems here. (a) method resolution picks up the wrong method ( Array.operator()(Int) instead of Array.operator()(Point) ), and thus tries to generate a coercion (b) the code for generating dynamic checks fails to replace the this from the Array class method argument type with the receiver, thus confusing the typechecker. Yoav, can you please take a look? We may have to change our dynamic check generation strategy to detect such cases and default to something like your closure generation code instead.

Yoav Zibin added a comment - 16/Mar/11 4:19 PM Fixed in revision 20781. The original code now gives this error: $ x10c -VERBOSE_CALLS Hello.x10 C:\cygwin\home\Yoav\test\Hello.x10:30: A property type cannot be a type parameter. 1 error. But if you remove the generic parameter from Number, it works fine: public class Hello { public static def main(args: Array[ String ]) { Console.OUT.println( new Number (['1','2','3']) ); } static type Digit = Char; static type Num = Array[Digit](1); static class Number (baseNum:Num, digits: Int) { def this (n:Num) : Number { this .baseNum == n } { property(n, n.size); } public def toString() : String { var s: String = ""; for (d:Point in baseNum) s += baseNum(d); // generates a dynamic call return s; } } } $ x10c -VERBOSE_CALLS Hello.x10 C:\cygwin\home\Yoav\test\Hello.x10:28: Generated a dynamic check for the method call. Yoav@YoavLaptop ~/test $ x10 Hello 123

Igor Peshansky added a comment - 23/Mar/11 4:35 PM The original issue is still present – rejecting the generic property was a red herring. The following code demonstrates the problem: public class XTENLANG_2370 { static type Digit = Char; static type Num = Array[Digit](1); static def Number [T](baseNum:T){T<:Num} : String { var s: String = ""; for (d:Point in baseNum) s += baseNum(d); return s; } }

Yoav Zibin added a comment - 28/Mar/11 3:31 PM Fixed in revision 20996.

David Grove added a comment - 22/May/11 8:36 AM bulk close of all 2.2.0 resolved issues.