Add reflective fallback for useK2 to support Kotlin 2.3.0+#95
Merged
ZacSweers merged 2 commits intoZacSweers:mainfrom Dec 5, 2025
Merged
Conversation
ZacSweers
approved these changes
Dec 5, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a defensive
getUseK2Valuehelper to handle the removal ofuseK2in Kotlin 2.3.0+.In newer Kotlin versions, the
getUseK2()property no longer exists, causing reflective lookups to fail.To ensure forward compatibility, the new method attempts to read
useK2via reflection when available, and safely falls back to the Kotlin 2.3.0+ default behavior (useK2 = true) when the property or its provider cannot be accessed.useK2only when the property exists (older Kotlin versions).true.getUseK2()in Kotlin 2.3.0+.