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.

Sign up for GitHub

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

Jump to bottom

[KSP2] The JVM names of internal members are not mangled #1826

Closed
kuanyingchou opened this issue Apr 8, 2024 · 1 comment
Closed

[KSP2] The JVM names of internal members are not mangled #1826

kuanyingchou opened this issue Apr 8, 2024 · 1 comment
Labels
bug Something isn't working duplicate This issue or pull request already exists P1 major features or blocking bugs
Milestone
2.0

Comments

@kuanyingchou
Copy link
Collaborator

kuanyingchou commented Apr 8, 2024 •
edited
Loading

This may be part of #1640. For example, with:

class MyClass {
    internal fun a() = TODO()
}

Calling resolver.getJvmName() on the function we'll get a in KSP2 but a$main in KSP1.
@ting-yuan ting-yuan added bug Something isn't working P1 major features or blocking bugs labels Apr 24, 2024
@ting-yuan ting-yuan added this to the 2.0 milestone Apr 24, 2024
@ting-yuan ting-yuan added the duplicate This issue or pull request already exists label Apr 24, 2024
@ting-yuan
Copy link
Collaborator

Yes, this is #1640

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working duplicate This issue or pull request already exists P1 major features or blocking bugs
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
2 participants
@kuanyingchou @ting-yuan