0325ffaa01
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