Skip to content
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

[KSP2] Resolver.mapToJvmSignature() is not consistent #2109

Closed
kuanyingchou opened this issue Sep 18, 2024 · 0 comments · Fixed by #2130
Closed

[KSP2] Resolver.mapToJvmSignature() is not consistent #2109

kuanyingchou opened this issue Sep 18, 2024 · 0 comments · Fixed by #2130
Milestone

Comments

@kuanyingchou
Copy link
Collaborator

I'm getting inconsistent results when calling Resolver.mapToJvmSignature() on inline value classes. It always returns the underlying type in KSP1, but it sometimes returns the wrapper type in KSP2.

Repro: kuanyingchou@5746554

In the repro It returns different results for f's return type before and after another mapToJvmSignature call:

before: f: LMyInlineClass;
after: f: I
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants