I’d like to ask why plugins are not supported. Is ...

# k2-adopters

[natario1]

I’d like to ask why plugins are not supported. Is it because K2 changes the plugins API so all plugins must be adapted, or is it because it keeps the API but the underlying implementation is not there yet?

I am starting to work on my first plugin this week and I wonder if I should consider/know about K2 when designing the plugin.

[mglukhikh]

K2 changes the plugins API (its frontend part). In 1.7.20-Beta we'll have some plugins supported (allopen, noargs, parcelize, lombok, atomicfu, sam with receiver).

Also cc @dmitriy.novozhilov

[dmitriy.novozhilov]

K2 compiler API is completely different from K1 API, so it took some time to migrate official plugins to it
If you are interested in compiler plugins I suggest you to check #compiler channel, it contains some discussions about K2 API

[natario1]

Thanks 👍 so AFAIU it’s an unfortunate moment to start a new plugin, since API is quite different, K2 is alpha and yet coming relatively soon. I’ll go with the old API for now.

[dmitriy.novozhilov]

K2 affects mostly frontend API, so it's quite safe to use IrGenerationExtension