heads up: type annos issue

Jonathan Gibbons jonathan.gibbons at oracle.com
Fri Nov 30 11:17:59 PST 2012

Yesterday, Bhavesh reported that while working on type annotations 
support for javadoc, he noted that when he put a type annotation on a 
wildcard bound (which may have been Object), it ended up on *all* 
instances of Object, and thus showed up throughout the javadoc for the 
class. We suspect this is due to the type annotation being stored in the 
wrong place. Bhavesh will be following up with detailed evidence, but in 
the meantime, have you seen anything like this?

Would it help to to have a type/symbol printer that pretty prints the 
type/symbol showing all annotations?  That way we can (a) take javadoc 
out of the loop here, (b) write test cases more easily/

-- Jon

More information about the type-annotations-dev mailing list