Hey guys, remember the library for coroutine wrappers created from annotations? It's now called Koru, I've fixed a few things about it and wrote an introductory article https://medium.com/futuremind/handling-kotlin-multiplatform-coroutines-in-swift-koru-4a80b93f232b. Enjoy 🙂

Is there a reason, why did you implemented it as annotation processor, not as a kotlin compiler plugin. I am not judging your decision, just trying to learn rationale in a decision process.

@Michal Harakal I'm still not sure about this part tbh. I guess I was trying to start with what the big guys do, e.g. moshi or dagger. One thing that I will try to do is to get rid of explicit path to kapt dir, it's annoying and I don't see that in all the daggers. Other than that, not sure what big advantage of one over another might be.

I hadn't thought kapt would work for something like this because it's jvm-based.

The processor module was at some point a pure jvm module and it generated kotlin via kotlinpoet which was then used as kotlin native without problem. I only changed it from pure jvm to multiplatform because of some weird issues with IDE and integration tests

Hi @Michal Klimczak. I’m trying to build a local annotation processor for my project, that’s how I found this thread. Your source code already helped with some issues, so thank you! But also I’ve faced a couple of issues, could you take a look at my questions(https://kotlinlang.slack.com/archives/C3PQML5NU/p1618241893017100) in case you’ve faced some?