-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adapt WHEN_WITHOUT_ELSE
according to new features of Kotlin 1.6
#1149
Comments
I am not sure if it is possible to tell whether else block is redundant or not without compiling. |
I think this can be considered similar to #1168 : we don't have enough information to reason about |
### What's done: * changed behavior with expressions that look like enum entries of when: now if all the entries look like enum entries, WHEN_WITHOUT_ELSE rule is ignored * added tests (#1149)
### What's done: * changed behavior with expressions that look like enum entries of when: now if all the entries look like enum entries, WHEN_WITHOUT_ELSE rule is ignored * added tests (#1149)
### What's done: * changed behavior with expressions that look like enum entries of when: now if all the entries look like enum entries, WHEN_WITHOUT_ELSE rule is ignored * added tests (#1149)
### What's done: * changed behavior with expressions that look like enum entries of when: now if all the entries look like enum entries, WHEN_WITHOUT_ELSE rule is ignored * added tests (#1149)
### What's done: * changed behavior with expressions that look like enum entries of when: now if all the entries look like enum entries, WHEN_WITHOUT_ELSE rule is ignored * added tests (#1149)
* Adapt WHEN_WITHOUT_ELSE according to new features of Kotlin 1.6 ### What's done: * changed behavior with expressions that look like enum entries of when: now if all the entries look like enum entries, WHEN_WITHOUT_ELSE rule is ignored * added tests (#1149)
### What's done: * improved autofix: now we don't use `let` and `run` in some cases * added tests (#1149)
* Improve autofix in AVOID_NULL_CHECKS rule ### What's done: * improved autofix: now we don't use `let` and `run` in some cases * added tests (#899) * Improve autofix in AVOID_NULL_CHECKS rule ### What's done: * improved autofix: now we don't use `let` and `run` in some cases * added tests (#899) * Improve autofix in AVOID_NULL_CHECKS rule ### What's done: * improved autofix: now we don't use `let` and `run` in some cases * added tests (#899) * Improve autofix in AVOID_NULL_CHECKS rule ### What's done: * improved autofix: now we don't use `let` and `run` in some cases * added tests (#899) * Improve autofix in AVOID_NULL_CHECKS rule ### What's done: * improved autofix: now we don't use `let` and `run` in some cases * added tests (#1149) * Improve autofix in AVOID_NULL_CHECKS rule ### What's done: * improved autofix: now we don't use `let` and `run` in some cases * improved autofix: now we count statements, not lines * added tests (#1201) * Improve autofix in AVOID_NULL_CHECKS rule ### What's done: * improved autofix: now we don't use `let` and `run` in some cases * improved autofix: now we count statements, not lines * added tests (#1201) * Improve autofix in AVOID_NULL_CHECKS rule ### What's done: * improved autofix: now we don't use `let` and `run` in some cases * improved autofix: now we count statements, not lines * added tests (#1201) Co-authored-by: sanyavertolet <alexander.frolov@huawei.com> Co-authored-by: Andrey Kuleshov <andrewkuleshov7@gmail.com>
Now our 'generated else block' is treated as a compiler warning sometimes:
causes
The text was updated successfully, but these errors were encountered: