I've got an interesting bug report (with a repro) ...

# compiler

[Zac Sweers]

I've got an interesting bug report (with a repro) that comes from kotlinc's IC in a specific path
• A KSP processor generates a declaration in its KspTask
• The KotlinCompile task compiles this declaration, my compiler plugin (Metro) processes it and generates nested class declarations in FIR
• A subsequent incremental compilation reports The following LookupSymbols are not yet converted to ProgramSymbols for those symbols
@ralf filed a detailed report and repro link here.

It seems to come from this line, and I wonder if there is another edge case that may need to be carved out above it? I'm not sure how to debug this as attaching a debugger/running the compiler in process disables IC 😕

[dmitriy.novozhilov]

Could you please report a YT issue?
It seems relevant to my current work regarding IC and plugins (KT-75864).

[Zac Sweers]

done https://youtrack.jetbrains.com/issue/KT-80412/The-following-LookupSymbols-are-not-yet-co[…]ror-when-generating-nested-classifiers-from-KSP-generated

[Oliver.O]

@dmitriy.novozhilov In KT-75864 you were looking for use cases. I have a compiler plugin generating top-level declarations with successful IC integration tests for Kotlin versions 2.0.0 up to 2.2.20-RC. Maybe you'd want would add that to your use case list.

[dmitriy.novozhilov]

Could you please add a comment to the issue itself?

[Oliver.O]

Sure. I just wanted to ask first, because the issue seemed almost completed (marked "ready for review").

[dmitriy.novozhilov]

Please do. This ticket is about the simplest implementation, and my request for use-cases is needed to understand if we need more sophisticated one.

[Oliver.O]

Done.