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

Handle template parameters in NonClassOrInterfaceType correctly #146

Open
joorei opened this issue Jun 7, 2024 · 0 comments
Open

Handle template parameters in NonClassOrInterfaceType correctly #146

joorei opened this issue Jun 7, 2024 · 0 comments
Labels
bug/mistake potential Further investigations may reveal invalid behavior or the likelyhood of incorrect library usage. help wanted Extra attention is needed
Milestone

Comments

@joorei
Copy link
Collaborator

joorei commented Jun 7, 2024

Unlike NonClassOrInterfaceType, NonClassOrInterfaceType can be used to represent primitive types and works well for bool, int or even int<0,max>. However, it does not handle template parameters correctly, which are relevant in types like iterable or array. getAllFullyQualifiedNames will always return an empty array, which is not correct for something like iterable<\Exception>. getTemplateParameter will simply always throw an exception.

@joorei joorei added help wanted Extra attention is needed bug/mistake potential Further investigations may reveal invalid behavior or the likelyhood of incorrect library usage. labels Jun 7, 2024
@joorei joorei added this to the 1.0.0 milestone Jun 7, 2024
@joorei joorei changed the title Handle generics in NonClassOrInterfaceType correctly Handle template parameters in NonClassOrInterfaceType correctly Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug/mistake potential Further investigations may reveal invalid behavior or the likelyhood of incorrect library usage. help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant