No, and I'm happy there's none. It could encourage...

# compiler

[louiscad]

No, and I'm happy there's none. It could encourage people to write poor code with the excuse of build speed, that would make maintenance slower instead.

kapt is slow though, because it's not incremental yet (unless you already use 1.3.30 with EAP and your kapt dependencies have incremental support), but kapt is mainly Java legacy that is replaced by things like SQLDelight, kotlinx.serialization, delegates, extension functions, coroutines, data classes and more great features that are actually faster than annotation processors to compile.

[gildor]

I doubt that SQLDelight is faster, it just a bit different way to generate code, when you generate it by request and mostly in a separate module

[louiscad]

In my experience, it's faster than Room annotation processor. SQLDelight takes between 1 and 3 seconds to generate code most of the time.

[louiscad]

The numbers I have in mind for Room are about 8 seconds. But the actual database schema may have an influence, they were not in the same project, so no equivalence. A benchmark could be interesting.

[gildor]

they were not in the same project

exactly

[gildor]

of course, one of them (like SQLDelight) may generate less code, or code that compiled faster, but general way is the same (generate some code in additional compilation step, than compile it)