program crashes javac following recent updates
wdietl at gmail.com
Thu Jul 25 07:45:58 PDT 2013
my change definitely fixes the reported crash, but it might now put
type annotations on a ClassSymbol instead (or in addition?) of on the
I think this might be happening because that code is probably visited
twice, once before and once after becoming its own top-level class.
Steve, we previously discussed having additional tests that ensure
that the Lambda conversion puts type annotations on the right Symbols.
None of the existing tests failed additionally after my change, so I'm
not sure whether I broke this or not.
Could you point us to test cases that ensure that type annotations
on/within Lambdas are converted correctly?
On Wed, Jul 24, 2013 at 11:53 PM, Werner Dietl <wdietl at gmail.com> wrote:
> I pushed a fix:
> Please let me know whether this looks good.
> cu, WMD.
> On Wed, Jul 24, 2013 at 6:32 PM, Jonathan Gibbons
> <jonathan.gibbons at oracle.com> wrote:
>> Maurizio has reported that a test program has started crashing as a result
>> of a recent push from the type-annotations forest. Do you have time to take
>> a look? You can find details here:
>> -- Jon
More information about the type-annotations-dev