It probably is a bug. Looking at what happens it is probably something to do with allocation of local slots. It should however not keep trying this long. In this example inlining is a bad thing to do as quite some nontrivial stuff happens in joinItems and even in join. You are absolutely blowing up the code size without real reason to do so.The JVM is quite efficient in doing these things for you if it is the right thing to do.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
|
Deep nested inline functions run slowly and can causes an error at compile
|
3 | 3502 | January 20, 2016 | |
|
High CPU load in IDE when making any code change
|
5 | 1549 | July 25, 2013 | |
| Why joinToString and joinTo are not inline? | 5 | 1456 | January 21, 2017 | |
| Compiler optimizations | 3 | 2229 | December 8, 2015 | |
| Inlining Tiny Methods | 8 | 4964 | August 27, 2020 |