JSR 308 implementation: information needs

Michael Ernst mernst at cs.washington.edu
Sat Jan 12 04:51:26 PST 2013


Alex-

Thanks for suggesting that we make an explicit list of to-do items.  Here
are some specific things that we could use from Oracle, the lack of which
has slowed us down.

1. We need a reply to Werner's Dec 31 message about introducing
Type.AnnotatedType, to know whether that is the right direction or whether
Jon wants to investigate alternatives:
http://mail.openjdk.java.net/pipermail/type-annotations-dev/2012-December/000358.html

2. We need a reply to Werner's messages of January 7 about when type annotation
positions are determined, again to know in what direction to take the code.
http://mail.openjdk.java.net/pipermail/type-annotations-dev/2013-January/000379.html
http://mail.openjdk.java.net/pipermail/type-annotations-dev/2013-January/000381.html

3. We could use details about javac's translation of lambda, which will
greatly help us implement the (vague) JSR 308 spec for bytecode
representation of lambda type arguments that you and I agreed on in our
January 10 phone call.

4. Joel hasn't committed anything to the type-annotations forest yet, so we
don't know much about his status.  It would be good to either have more
insight or (even better!) to have assurance that this won't affect
schedule, no matter what happens.

5. We need a schedule for when Jon plans to generate the one big changeset
to push to TL.  When has he allocated time for that, and how much time has
he allocated?

Thanks very much!

		    -Mike


More information about the type-annotations-dev mailing list