Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: X10 2.1.1
-
Fix Version/s: X10 2.2
-
Component/s: Hot Defect, X10 Compiler: Front-end Typechecking
-
Labels:None
-
Environment:Linux on power
-
Number of attachments :
Description
See RTC-876
Issue Links
- is depended upon by
-
XTENLANG-2584
X10 2.2 frontend issues (umbrella)
-
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.