kotlin-multiplatform-libsodium VS ksp

Android (Google play store): https://play.google.com/store/apps/details?id=com.ionspin.me...

We also have a iOS build for testing through TestFlight available on this link: https://testflight.apple.com/join/ohRS4Pd4

You can learn more about mementō and the company here http://www.ionspin.com

If you want to share your feedback directly with us you can send it to [email protected], it'll get forwarded directly to all of our inboxes.

I'll also be here for a couple of hours to answer all of your questions.

Ugi

[1] Kotlin wrapped libsodium - https://github.com/ionspin/kotlin-multiplatform-libsodium

You can find the library here: https://github.com/ionspin/kotlin-multiplatform-libsodium

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.