Dmitriy Novozhilov
419f54259c
Previously helpers from checkType.kt was in special package, and
if directive was enabled then test runner (`AbstractDiagnosticTest`)
injected additional imports to test files and removed them after test
was completed.
It's very hard to support such behavior in new test infrastructure so
there was a decision about changing `CHECK_TYPE`:
1. All helpers from `checkType.kt` now stays in default package
2. `CHECK_TYPE` only adds `checkType.kt` to set of analyzed files
and don't modify their content
For test which are written in default package (most of tests actually)
there are no changes. On the other hand if there is a test where dev
want to use checkType functions in testfile with some package then he
should explicitly import functions which he needed (`checkSubtype`,
`checkType`, `_`)
37 lines
1.0 KiB
Kotlin
Vendored
37 lines
1.0 KiB
Kotlin
Vendored
// !CHECK_TYPE
|
|
|
|
//KT-2324 Can't resolve generic by type of function result
|
|
package i
|
|
|
|
//+JDK
|
|
import java.util.*
|
|
import checkSubtype
|
|
|
|
fun <T, K> someFunction(list: List<T>, transform: (T) -> K): List<K> {
|
|
val result = arrayList<K>()
|
|
for (i in list) {
|
|
result.add(transform(i))
|
|
}
|
|
return result
|
|
}
|
|
|
|
fun testSomeFunction() {
|
|
val result1 = someFunction(arrayList<Int>(1, 2), {checkSubtype<Int>(it)}) //type of result1 is List<Int>
|
|
assertEquals(1, result1.get(0)); //OK
|
|
|
|
val result2 = someFunction(arrayList<Int>(1, 2), {it}) // type of result2 is List<DONT_CARE>
|
|
checkSubtype<List<Int>>(result2)
|
|
assertEquals(1, result2.get(0)); //resolved to error element
|
|
}
|
|
|
|
//---------------------------------
|
|
fun assertEquals(expected: Any?, actual: Any?, message: String = "") {
|
|
}
|
|
|
|
fun <T> arrayList(vararg values: T) : ArrayList<T> = values.toCollection(ArrayList<T>(values.size))
|
|
|
|
fun <T, C: MutableCollection<in T>> Array<T>.toCollection(result: C) : C {
|
|
for (element in this) result.add(element)
|
|
return result
|
|
}
|