With `kotlin.experimental.tryK2` the idea is that ...
# eap
w
With
kotlin.experimental.tryK2
the idea is that if I turn it on, then Kotlin will automatically figure out which compilation tasks can use K2 and which can't? So if some modules use Kapt then K2 will be skipped there (I think Kapt is still not supported in K2?), but for other modules K2 will be used?
t
If you have somewhere explicitly configured LV - it will stay as is. Though default LV will be changed to
2.0
The idea not to touch explicitly configured LV is that it was configured for some unknown to us reason and most probably it will not work with LV 2.0
currently kapt will not fail if you configure LV 2.0, but internally it will fallback to old backend. This will change in 1.9.20