Use a type refiner#1
Merged
Merged
Conversation
Owner
Author
|
This works incredibly well... I'm very tempted to just merge it. The usage of reflection is scary, but |
Avoid exceptions Upgrade to Kotlin 2.3.20-Beta1
Owner
Author
|
Since this branch has become my main focus, and given how well it works, I'm merging it. We can always go back to the original approach if necessary. This is ultimately less hacky |
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.
This sadly requires reflection...
The reflection is used to create an instance of
TypeComponentswith a customConeInferenceContext, which is used to inject a type refiner that automatically appliesK, and it also returns the canonical K representation as a supertype to every generic type.It also tracks the original expanded version of every K type, and provides that as a supertype too when asked. That means that
expandTocalls are largely unnecessary, and, in fact, are no longer special or intrinsic.It's much nicer to use though, and uses less hacky compiler tricks.