Checker rule for fixed Kotlin issues


#1

This is a request for a lint check for fixed Kotlin issues.

Motivation: KT issues sometimes require writing alternate or additional code.
Common practice is to mark these workarounds like in LexicalScopeStorage.kt

        //TODO: could not use += because of KT-8050
        variablesAndClassifiersByName!![name] = variablesAndClassifiersByName!![name] + descriptorIndex

It would be nice if each language release came with a lint rule that marks lines beginning with //TODO (or/and some new, tbd. tag) and which contain a resolved KT-issue id.

This would make it much easier to clean up the code once issues get fixed.