# Should we be reporting FindBugs issues?

**URL:** <https://discuss.kotlinlang.org/t/should-we-be-reporting-findbugs-issues/2105>\
**Category:** Uncategorized\
**Created:** [November 22, 2016, 8:01pm UTC](https://discuss.kotlinlang.org/t/should-we-be-reporting-findbugs-issues/2105 "2016-11-22T20:01:41Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![yole](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.kotlinlang.org/yole/32/1425_2.png) [@yole](https://discuss.kotlinlang.org/u/yole)\
**Post date:** [November 27, 2016, 9:03am UTC](https://discuss.kotlinlang.org/t/should-we-be-reporting-findbugs-issues/2105/2 "2016-11-27T09:03:19Z")

</div>

We’re aware of inefficiencies in the Kotlin-generated bytecode, and we plan to address them when switching to a new implementation of the JVM backend in Kotlin 1.2. At this time, I don’t think it’s worth filing issues for problem that FindBugs detects, because we won’t address them anyway, and it’s likely that they will go away after the rewrite.

---

_[View the full topic](https://discuss.kotlinlang.org/t/should-we-be-reporting-findbugs-issues/2105)._