Community
Participate
Working Groups
A synthetic access method (e.g., for this$0) will be generated with wrong signature if tsuper role is read from .class file. This manifests in a method signature with a role interface parameter, but inside the method, this argument is treated as the role class. Observed in OTSample-FlightBonus when only touching/saving role file GUIConnector/FlightBonusDialog.
Created attachment 193864 [details] test & proposed fix The problem is rooted in the fact that copy inheritance triggers (via resolveGeneratedMethod -> resolveTypesFor) wrapping of types in the method signature even for copies of synthetic methods. Solved by passing one more flag into resolveTypesFor. Test results pending.
OTJLD tests pass. Patch has been committed as r1443,4
Verified for 0.8M7 using build 201104300913