Files
kotlin/compiler/testData/codegen/bytecodeText
Dmitry Petrov 9d1901fc7c Intrinsify some mismatching range/element combinations for in/in!
It's safe to upcast integer types to Long,
floating-point types to Double.
So we don't have to create a range instance for cases such as

fun testLongInInt(x: Long, a: Int, b: Int) =
    x in a .. b

which is equivalent to

fun testLongInInt(x: Long, a: Int, b: Int) =
    x in a.toLong() .. b.toLong()
2017-07-10 10:51:26 +03:00
..
2016-02-01 18:32:12 +03:00
2016-02-01 22:20:30 +03:00
2016-02-01 22:20:30 +03:00
2015-04-07 13:08:51 +03:00
2015-10-27 12:02:27 +03:00