Nikolay Lunyak
603b46e531
Passing `EXTENSION_RECEIVER` when processing `noReceiver` looks like a mistake in general. This change is backed by the `hidesMembers` and `memberWithHidesMemberAnnotationVsMemberWithout` tests. The exact reason with `memberWithHidesMemberAnnotationVsMemberWithout` is that it first checks `@HidesMembers` candidates, only takes the `kotlin/collections/Iterable<T>.forEach`, but then yields `InapplicableWrongReceiver`, because `explicitReceiverKind = EXTENSION_RECEIVER` (which is strange, because we really don't have an explicit receiver). Then we visit the same scope once more (now for all candidates) and take 2 functions: - `kotlin/collections/Iterable<T>.forEach` - `kotlin/sequence/Sequence<T>.forEach` ...and they both result in `RESOLVED`, because this time `explicitReceiverKind = NO_EXPLICIT_RECEIVER`. This change ensures the first candidate we see while checking `@HidesMembers` is taken as `RESOLVED`. ^KT-55503 Fixed
13 lines
289 B
Kotlin
Vendored
13 lines
289 B
Kotlin
Vendored
fun foo() = withIntList {
|
|
withStringSequence {
|
|
forEach { line ->
|
|
line.<!UNRESOLVED_REFERENCE!>rem<!>(1)
|
|
line.length
|
|
}
|
|
}
|
|
}
|
|
|
|
fun withIntList(x: List<Int>.() -> Unit) {}
|
|
|
|
fun <T> withStringSequence(action: Sequence<String>.() -> T): T = TODO()
|