You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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, becauseClassDeclaration
extendsTypeDeclaration
, but we should never give you aClassDeclaration
in this phase. If an implementation gave youClassDecaration
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 toTypeDeclaration
, butClassDeclaration
would not implement it.The text was updated successfully, but these errors were encountered: