Hi @radekm, nothing really since that kind of transformation will soon be unsupported for the very reason you showed there.
The issue here is that in place tree transformations require generation of synthetic descriptors and an IDE plugin but there is no solution for code locations or coordination with the actual document in the IDE. For that reason we are gonna drop support for Transform.replace and support only Transform.newSources until FIR is released and there is a solution for this kind of transformation that does not require users to install an IDE plugin.
1 year ago
Ok, makes sense. Thanks. I think I will be able to circumvent it by calling the original class with some crazy name like
class `temp Foo`()
and then leaving it in AST
1 year ago
too bad, although many things could be achieved with generating new sources, sometimes it is really not optimal
I have a use case where I would either replace in place or generate loooots of synthetic methods
Would FIR actually bridge the compiler and intelliJ? Sorry if it’s a stupid question, I’m not much into intelliJ plugins and code analysis there