-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove workaround that disables usePreciseJavaTracking
with Kotlin 1.8 support
#670
Comments
Could it remove the workaround if running in a kotlin 1.8 setup? |
Absolutely! |
…ed anymore with Kotlin 1.8. Fixes #670
…ed anymore with Kotlin 1.8. Fixes #670
…ed anymore with Kotlin 1.8. Fixes #670
…ed anymore with Kotlin 1.8. Fixes #670
Hey! That is a great news! |
Yes, that solves a different problem and still is required. |
Thanks for your reply! I assume that stated problem is described here, but Kotlin issue's status is "Fixed" in 1.8.0. Disabling incremental compilation for kapt in our codebase makes huge performance drawback on incremental builds, so it'll be really great if you could provide some details. |
The README got a little out of date. I'm addressing this here: #685 I'm sorry about the confusion. |
Great! Thanks a lot for clarification. |
The issue KT-38576 has been resolved with Kotlin 1.8 and the workaround is no longer needed. When Anvil drops support for Kotlin 1.7 it should also remove this workaround.
The text was updated successfully, but these errors were encountered: