![]() ![]() When designing KSP, we thought about what annotation processing would look like for Kotlin if we built it from the ground up. KAPT can be slow to run, though, since it requires generating intermediate Java stubs that can then be ingested by the Java annotation processing system. Annotation processors like Room are ubiquitous on Android and rely on Java annotation processing compatibility through the Kotlin Annotation Processing Tool (KAPT). ![]() One of the biggest challenges with compiling Kotlin code is that Kotlin doesn’t have a native annotation processing system. Many developers iterate on and deploy apps dozens of times a day, so having to sit around waiting for a slow build can be very time consuming. The #1 request we hear from Kotlin developers is to make build speeds faster. You can check out the open source code and documentation in the KSP GitHub repository. KSP is compatible with the Kotlin 1.4.30 release and onwards. ![]() KSP offers similar functionality to KAPT, however it’s up to 2x faster, offers direct access to Kotlin compiler features, and is being developed with multiplatform compatibility in mind. Today we are excited to announce the alpha of Kotlin Symbol Processing (KSP), an all-new tool for building lightweight compiler plugins in Kotlin. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |