1--- 2name: Design considerations 3about: We didn't think things through? 4title: '' 5labels: design 6assignees: '' 7 8--- 9 10<!-- 11This is a place for issue reports that are not exactly bugs (wrong unintentional behavior) but for our library behaving suboptimally (though this could have been intentional). 12 13**Double-check** 14 15* If the behavior is strange, surprising, and undocumented, it could be a good idea to file a "Bug report" instead. 16* Is this still relevant with the latest version of the library? We could have changed this already. 17* Maybe there are good reasons for the existing behavior. Please try searching for existing discussions of the problem. 18* Are you using the right abstraction? Consider asking on [StackOverflow](https://stackoverflow.com/) or the [Kotlin Slack](https://surveys.jetbrains.com/s3/kotlin-slack-sign-up). Maybe your need is better solved by some other abstraction entirely. 19 20--> 21 22**What do we have now?** 23 24Preferably with specific code examples. 25 26**What should be instead?** 27 28Preferably with specific code examples. 29 30**Why?** 31 32The upsides of your proposal. 33* Who would benefit from this and how? 34 - Would it be possible to cover new use cases? 35 - Would some code become clearer? 36 - Would the library become conceptually simpler? 37 - etc. 38 39**Why not?** 40 41The downsides of your proposal that you already see. 42* Is this a breaking change? 43* Are there use cases that are better solved by what we have now? 44* Does some code become less clear after this change? 45* etc. 46