Extend generic advice to apply to parameters, too.

[stephan]

Rule OTJLD §4.9.3 defines generic advice wrt. covariant return types. This rule should be extended to

• cover variance not caused by inheritance but by callin binding (e.g., listing several base methods)
• cover variance in parameters, too.

This involves small changes to the OTJLD, compiler & tests.

[stephan]

Two-way compatibility of return types is tested in 4.1.40-otjld-callin-replace-compatibility-1 ff. These tests are fixed by r18139, r18142.
Several tests are in fact provided/inspired by Bruno de Fraine.

Initial tests regarding type variables for parameters are in

• 4.4.5-otjld-callin-replace-casts-arg-1f (error case), fixed in r18141.
• 4.4.5-otjld-callin-replace-casts-arg-1 (positive) is fixed in r18144, but two FIXMEs remain in CallinMappingDeclaration and CallinImplementor, resp.

[stephan]

New tests:

Different return types of multiple base methods:

• 4.1.40-otjld-callin-replace-compatibility-9 works in r18190
• 4.1.40-otjld-callin-replace-compatibility-9s fixed in r18190

Different parameter types of multiple base methods:

• 4.1.40-otjld-callin-replace-compatibility-10 fixed in r18190
• 4.1.40-otjld-callin-replace-compatibility-10s fixed in r18190

Parameter mapping:

• 4.1.40-otjld-callin-replace-compatibility-11 not yet

[stephan]

More:

Combination with parameter mappings (fixed in r18193, r18194):

• 4.1.40-otjld-callin-replace-compatibility-11
• 4.1.40-otjld-callin-replace-compatibility-12

Duplicate use of type parameters (fixed in r18195):

• 4.1.40-otjld-callin-replace-compatibility-13
• 4.1.40-otjld-callin-replace-compatibility-14

[stephan]

Together with above mentioned patches, the new section OTJLD §4.10 as of r18207 plus r18208 completes this issue.