Creating a clone of a javac.code.Type
Jonathan Gibbons
jonathan.gibbons at oracle.com
Mon Jan 14 14:59:32 PST 2013
On 12/31/2012 01:43 AM, Werner Dietl wrote:
> Please let me know what you think of this significant change and
> whether this is the direction you wanted things to go.
Yes, I think this is the direction that we need to go.
I think using an AnnotatedType that augments an underlyingType with
annotations is in general preferable to being able to store annotations
on types, partly from the storage point of view, and partly from the
cloning issue that we ran into.
At least in the first patch, I didn't see an override on Type.getTag.
It is not clear to me that all of the methods should just delegate to
underlyingType and ignore the annotations. For example, what about
AnnotatedType.map -- should that not map any types in the annotations as
well?
-- Jon
More information about the type-annotations-dev
mailing list