kotlin-inject VS ksp

Depending on how you use Anvil, there are definitely things that are missing/not as straightforward, e.g. https://github.com/evant/kotlin-inject/issues/212

I haven't used koin in a couple years since my newer jobs are using hilt and dagger/anvil for the compile time safety. In my personal projects I have been using kmp which when I started two years ago, koin was in alpha which was why I decided to use kodein. Which koin is stable in kmp, although kotlin-inject seems like a promising kmp compile time di in place of dagger.

I would suggest looking at Kotlin-Inject, it's a compile-time DI like Dagger and it's really pleasant to use.

Dagger/ hilt will not work on kmm being that they are java projects. One project that is similar to them though on kmm is kotlin-inject which might be something to look at.

I'd say it's second after this one. That one has multiplatform support in snapshot version, while mine is in alpha)

Interesting! Author of kotlin-inject here, I had originally looked at writing a compiler plugin and using IR but the lack of documentation and a non-stable api scared me away. Cool that you were able to get it to work.

google/ksp is one of the lightweight compiler plugin. We can easy to create compiler plugin with simple syntax. It's set as stable last year.

google/ksp is one of the lightweight compiler plugin which is developed by google. Some jetpack libraries are supporting that configures with ksp (ex: room).

Some guys consider it as a bug.https://github.com/google/ksp/issues/969

Links: GitHub Repo : https://github.com/aniketbhoite/ksp-my-event Google KSP Doc: https://github.com/google/ksp KotlinLang KSP Doc: https://kotlinlang.org/docs/ksp-overview.html

If you ever come back to it, check out https://github.com/google/ksp, it's relatively new but I think it might be a great fit for the project.

Fyi ksp handles tracking this for incremental builds, you may be able to see what they are doing?

I'd like to further iterate on all these patterns in some form of codegen library in the future, as compiler plugins start to mature. I'm hopeful for a multiplatform version of Kotlin Symbol Processing to help with this, though this won't be possible before Kotlin 1.5.20 at the earliest due to missing extension points in the Kotlin compiler. Fingers crossed for something this summer I guess.

Well, KSP is developed by Google, so you should ask them for more documentation, I think :) For compiler plugins -- yes, JetBrains should at some point invest some time and create at least the basic documentation for compiler plugin authors. But first of all, we need to create the public compiler API itself. We are going to do that after releasing the JS IR back-end.