Kotlin 1.4-M2 fixes the issue where the coroutines `Flow.collect` method from the `Flow` interface s...

# intellij

[Zach Klippenstein (he/him) [MOD]]

Kotlin 1.4-M2 fixes the issue where the coroutines Flow.collect method from the Flow interface showed up first in code completion, despite being effectively internal. How does that actually work? Is there some internal hard-coding that special-cases that particular method, or is there a way to use this trick in other code?

[Alexey Belkov [JB]]

You can see the commit in "VCS changes" tab in YouTrack.
https://youtrack.jetbrains.com/issue/KT-36808
https://github.com/jetbrains/kotlin/commit/4c6ea7c26a4fccabafd8e714555ea91d3282936f

[Zach Klippenstein (he/him) [MOD]]

It is hard-coded 😕 Would it be possible to automatically automatically lower the precedence of any method that is tagged with a RequiresOptIn.Level.ERROR? The compiler already knows it's going to raise an error in those cases, so it would seem useful to always push those down.

[Alexey Belkov [JB]]

Sure, can you please submit an issue to http://kotl.in/issue

[louiscad]

Submitted the feature request here: https://youtrack.jetbrains.com/issue/KT-40231

[Zach Klippenstein (he/him) [MOD]]

Thanks @louiscad, somehow I forgot to follow up on this