Files
kotlin-fork/compiler/testData/diagnostics/tests/when
Mikhail Zarechenskiy f702417655 [NI] Relax rules for call completion: require at least one constraint
It's enough to have at least one good constraint.

 Note that the whole algorithm can be a bit more general:
 we could check also Out<T>, In<T> and verify that T has good only
 lower constraint or upper constraint, but there are questions for
 types like Inv<Out<T>>, where T should have lower and upper constraints

 #KT-31514 Fixed
2019-05-29 02:14:00 +03:00
..
2016-05-16 15:38:13 +03:00
2016-05-16 15:38:13 +03:00
2016-05-16 15:38:13 +03:00
2016-05-16 15:38:13 +03:00
2016-05-16 15:38:13 +03:00
2016-05-16 15:38:13 +03:00
2016-01-22 10:41:55 +03:00
2016-01-22 10:41:55 +03:00
2016-01-22 10:41:55 +03:00
2015-12-01 10:36:40 +03:00
2015-12-01 10:36:40 +03:00
2016-05-16 15:38:13 +03:00