Bug fix: order of attribution of lazy constant values
Werner Dietl
wdietl at gmail.com
Mon Jan 28 00:00:32 PST 2013
Jon, all,
in a case study we uncovered a problem with the order of how type
annotations are attributed.
I pushed a test case and simple fix:
http://hg.openjdk.java.net/type-annotations/type-annotations/langtools/rev/dff2e8610acd
Note that the code in
comp.Attr.visitVarDef(JCVariableDecl)
which analyzes a variable initializer, is not executed for a lazy
constant value.
Is there a nicer place to unify these two separate calls of
memberEnter.typeAnnotate?
Could you file a bug and push this fix to TL?
Thanks,
cu, WMD.
--
http://www.google.com/profiles/wdietl
More information about the type-annotations-dev
mailing list