@yole, I understand about issue prioritization and having to triage issues otherwise the team will bog down. It is the reality of having to live with the resources we have, not the resources we would like to have. I would like to thank you for being honest about having set lower priority on some of these issues. There is no need to apologize for being human, being honest about it is the best action that can be taken and you have done that already.
As far as grumbling about lack of Kotlin features is concerned, sometimes you are lucky to get that. Many users will vote with their feet without feedback. Listening to the shrill of excitement from devotees can be misleading. The devotees are willing to overlook any and all issues, creating a wrong impression of an average user experience.
I was a relatively early adopter of Kotlin for production code, in my plugin I used pre-release Kotlin and stuck with it because I find it a beautiful language. I don't consider myself to be an expert in Kotlin nor do I care to push the language boundaries. I do have over 70k lines of Kotlin with over a year worth of production experience so don't consider my experience to be based on impressions from short term, limited use.
I did not open this topic to bitch about Kotlin or trying to put you or the Kotlin team on the defensive. Quite the contrary. I want Kotlin to succeed. I was sharing my experience to bring to your attention to the mundane and boring features that most developers would not find exciting which are causing a significant impact on productivity in Kotlin vs Java, in contrast to topics here which focus on missing language features to make Kotlin even more expressive.
I don't expect Kotlin support in the IDE to match Java for obvious business reasons. This is not to question JetBrains' commitment to Kotlin but to accept the reality that Java has and will continue to have more resources allocated to it for quite a while if not forever.
However, the quality of Kotlin support in the IDE leaves better to be desired: exceptions, index corruption, inability to handle invalid Kotlin code as occurs regularly when code is being edited, refactoring deleting code if it results in incomplete or incorrect Kotlin instead of leaving incomplete code as is, should not be a regular occurrence when using Kotlin.
Your honesty goes a long way to help address the unspoken perception that no one cares about mundane "low priority" features in Kotlin.