# Checker rule for fixed Kotlin issues

**URL:** <https://discuss.kotlinlang.org/t/checker-rule-for-fixed-kotlin-issues/5991>\
**Category:** Uncategorized\
**Created:** [December 28, 2017, 9:59am UTC](https://discuss.kotlinlang.org/t/checker-rule-for-fixed-kotlin-issues/5991 "2017-12-28T09:59:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tango24](https://avatars.discourse-cdn.com/v4/letter/t/74df32/32.png) [@tango24](https://discuss.kotlinlang.org/u/tango24)\
**Post date:** [December 28, 2017, 9:59am UTC](https://discuss.kotlinlang.org/t/checker-rule-for-fixed-kotlin-issues/5991/1 "2017-12-28T09:59:40Z")

</div>

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`

```auto
        //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.