A modern programming language that makes developers happier.

kotlinlang

I'm finding that annotation changes on classes do not (consistently) dirty classes that use them. A user reported it <https://github.com/ZacSweers/metro/issues/468|here> and I was able to reproduce it in a test <https://github.com/ZacSweers/metro/blob/main/gradle-plugin/src/functionalTest/kotlin/dev/zacsweers/metro/gradle/incremental/ICTests.kt#L711|here>. I'm able to work around it by generating a synthetic holder function in a generated class and copying the annotations over + recording a fake lookup to LookupTracker for IC to kick, but I'm curious if there's a better way to do this for just class annotations? IIRC this was improved a couple years back but I can't find a link handy

Wasn't it this one perhaps? <https://youtrack.jetbrains.com/issue/KT-57919/Store-all-annotations-in-Kotlin-metadata-on-JVM-under-a-flag|https://youtrack.jetbrains.com/issue/KT-57919/Store-all-annotations-in-Kotlin-metadata-on-JVM-under-a-flag>

possibly yeah. I thought there was a separate one for KGP's IC to make annotation changes invalidate (independent of metadata)

ahh ok I think that is the original issue after all per <https://github.com/square/anvil/issues/693#issuecomment-1519703641>

perfect, so hopefully it Just Works starting in 2.2

hmm, seems not. Just tested on my 2.2 branch and same issue still there