-
Notifications
You must be signed in to change notification settings - Fork 8
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
Names of anonymous classes cause issues #86
Labels
Comments
slarse
added a commit
that referenced
this issue
Mar 29, 2020
Not necessarily a complete solution, this might cause issues
This may have been fixed by 755b27b, but I'm really not sure |
As it turns out, just not resolving the name causes crashes when the type of an anonymous class is matched to any other type reference. So we must resolve the name (but we can fake it). |
slarse
added a commit
that referenced
this issue
Mar 29, 2020
slarse
added a commit
that referenced
this issue
Mar 29, 2020
slarse
changed the title
Names of anonymous functions cause issues
Names of anonymous classes cause issues
Mar 30, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The names of anonymous functions are integers, and these are arbitrary. However, Spork treats them as if they have meaning for the anonymous function, which can cause content conflicts on anonymous functions even if there are none.
A quick fix for this is to simply not resolve the names of anonymous functions. The downside of that is that there could end up being multiple anonymous functions in the tree with the same name, and I'm uncertain of what effects that may have.
The text was updated successfully, but these errors were encountered: