https://kotlinlang.org logo
Title
t

trevjones

07/23/2020, 1:20 AM
Anyone comfortable with throwing out a hand-wavey timeline for KSP landing in the main line kotlin artifacts? even if just an opt in basis similar to how NewInference is I can make a better argument for jumping on it for a few concepts I am cooking up.
t

Ting-Yuan Huang

07/23/2020, 1:22 AM
We are aiming to land in upstream before the end of 2020.
👍 4
🎉 3
t

trevjones

07/23/2020, 1:27 AM
thank you, this is promising work, keep it up!
👍 1
As I was thinking more about this. does it even need to be in the mainline? If it is a compiler plugin wouldn’t that mean I need only pull in a jar to the correct classpath once 1.4 ships? I need to go actually read some code on the topic… but figured I’d ask anyway.
t

Ting-Yuan Huang

07/24/2020, 5:17 AM
There are a few reasons. One is that people like and trust built-in functionalities. It's easier to maintain as well, because it'll be tested on each compiler release. There are also some compiler internal functions that are only (conveniently) available when compiled with
kotlinc
. We also need to make some changes in the compiler for features like multiple-round support.
t

trevjones

07/24/2020, 3:43 PM
I’d imagine the IDE and misc tooling story gets better when first party as well. and TY again!