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

Consider adding a ResolvedTypeReference class #5

Open
jakemac53 opened this issue Jun 24, 2021 · 0 comments
Open

Consider adding a ResolvedTypeReference class #5

jakemac53 opened this issue Jun 24, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@jakemac53
Copy link
Owner

This would be what you get when you introspect on types in the Declaration phase. Today, we give you a TypeDeclaration object, but that gets a bit confusing, because ClassDeclaration extends TypeDeclaration, but we should never give you a ClassDeclaration in this phase. If an implementation gave you ClassDecaration it would expose information that should only be available to directly annotated classes such as the members of that class.

We could avoid this situation by instead returning a ResolvedTypeReference, which would have an identical api to TypeDeclaration, but ClassDeclaration would not implement it.

@jakemac53 jakemac53 added the enhancement New feature or request label Jun 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant