Alexander Udalov f198a28276 Fix type parameter bound check in expect-actual checker ...

Also make TypeParameterUpperBounds a "strong" incompatibility, meaning
that non-actual members from platform module are _not_ going to be
matched to the expected members if this incompatibility exists between
them, and therefore NO_ACTUAL_FOR_EXPECT will be reported on the
expected declaration, instead of ACTUAL_MISSING on the platform member.
This is needed because the difference in type parameter upper bounds can
have effect on the function signature on the platform (e.g. on JVM,
Array<T> -> T[], but Array<T> -> Comparable[] if T : Comparable<T>), and
it would be incorrect to report ACTUAL_MISSING on the member that has
nothing to do with the expected declaration that happens to coincide
with it in everything except type parameter bounds

 #KT-21864 Fixed

2018-02-05 13:38:04 +01:00

..

functionTypeParameterBounds.kt

Fix type parameter bound check in expect-actual checker

2018-02-05 13:38:04 +01:00

functionTypeParameterBounds.txt

Fix type parameter bound check in expect-actual checker

2018-02-05 13:38:04 +01:00

genericMemberBounds.kt

Fix type parameter bound check in expect-actual checker

2018-02-05 13:38:04 +01:00

genericMemberBounds.txt

Fix type parameter bound check in expect-actual checker

2018-02-05 13:38:04 +01:00

membersInGenericClass.kt

…

membersInGenericClass.txt

…

typeParameterBoundsDifferentOrderActualMissing.kt

Fix type parameter bound check in expect-actual checker

2018-02-05 13:38:04 +01:00

typeParameterBoundsDifferentOrderActualMissing.txt

Fix type parameter bound check in expect-actual checker

2018-02-05 13:38:04 +01:00