azalea/kotlin-fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Introduce a workaround in interpreter tests to make them pass

Browse Source 
There is a problem with ranges and iterators. To work properly
they must be resolved firstly, before operator rangeTo.
This commit is contained in:
Ivan Kylchik
2021-08-04 14:16:18 +03:00
committed by TeamCityServer
parent 44e1b61e6c
commit 4f15bd4817
6 changed files with 26 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
compiler/testData/ir/interpreter/primitives/intMethods.kt
Vendored
+6
View File
@@ -1,3 +1,9 @@
// this hack is used to ensure that iterator will be resolved first
@CompileTimeCalculation internal class IntProgressionIterator(first: Int, last: Int, val step: Int) : IntIterator()
@CompileTimeCalculation public class IntRange(start: Int, endInclusive: Int) : IntProgression(start, endInclusive, 1), ClosedRange<Int>
@CompileTimeCalculation internal class LongProgressionIterator(first: Long, last: Long, val step: Long) : LongIterator()
@CompileTimeCalculation public class LongRange(start: Long, endInclusive: Long) : LongProgression(start, endInclusive, 1), ClosedRange<Long>
@CompileTimeCalculation fun compareTo(value: Int, other: Byte) = value.compareTo(other)
@CompileTimeCalculation fun compareTo(value: Int, other: Short) = value.compareTo(other)
@CompileTimeCalculation fun compareTo(value: Int, other: Int) = value.compareTo(other)