[FIR] Properly handle nested annotations on compiler-required annotation phase

There was a case when we visited the same declaration multiple times
  because of forward-referencing and visiting with designation
So because of this there were two changes required:
- remove assertion about visiting the same declaration twice (it's fine
  since we don't actually resolve annotations twice)
- not skipping resolution of class children if annotations on this class
  are already resolved

^KT-61388 Fixed
KT-62854
This commit is contained in:
Dmitriy Novozhilov
2023-10-19 17:10:56 +03:00
committed by Space Team
parent 80257dc58f
commit 0325ffaa01
7 changed files with 118 additions and 4 deletions
@@ -0,0 +1,13 @@
// ISSUE: KT-61388
// FILE: a.kt
@SinceKotlin
class Some
// FILE: b.kt
@SinceKotlin.SinceKotlin
class Other
// FILE: SinceKotlin.kt
annotation class SinceKotlin {
annotation class SinceKotlin
}