Just lost a couple of minutes for a strange issue ...

# coroutines

[Tolriq]

Just lost a couple of minutes for a strange issue with StateFlow. When using .collect {} it was automatically resolved to https://github.com/Kotlin/kotlinx.coroutines/blob/master/kotlinx-coroutines-core/common/src/flow/Flow.kt#L177 and did not propose the proper imports so obviously did not compile. Does anyone know why it resolved to that one without any related imports? (With 1.3.8) Manually adding the proper import fix the issue, but it's hard to figure out by default.

[octylFractal]

because a FlowCollector is a Single-Abstract-Method interface

[octylFractal]

so .collect {} is technically valid for it

[Tolriq]

Yes but why it's used without imports ? I would expect that it did not resolve and I had to import the proper one via alt+enter. Having default internal non usable thing used is weird.

[octylFractal]

because it's a method on flow? it's not an extension, it's always there

[octylFractal]

it's like asking "how do you use Any.toString() without importing it"

[Tolriq]

Well then having the extension name collision makes this strange to use, can't even use automatic IDE import resolution. Start by having an error then manual import does not sounds logical.

[octylFractal]

yes, I think it is a really weird design choice -- I don't recall why it is this way, and I thought there was a related issue for de-prioritzing it in completions, but I can't find it now

[octylFractal]

https://youtrack.jetbrains.com/issue/KT-36808

[Tolriq]

Oh nice it's fixed in 1.4 🙂 Thanks for the link.