Discrepancy for 'val' between javac and ecj.

akshattandon / projectlombok

Automatically exported from code.google.com/p/projectlombok

0 stars 0 forks source link

Discrepancy for 'val' between javac and ecj. #416

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

Map<String, Number> m = Collections.emptyMap();

val foo = randomBoolean ? m : Collections.<String, Number>emptyMap();

The above works in ecj, but not in javac.

Original issue reported on code.google.com by reini...@gmail.com on 17 Sep 2012 at 2:10

GoogleCodeExporter commented 9 years ago

Crud - we can't reproduce this at all. I guess it takes more than just the 
above sample code to trigger this bug because I can pretty specifically recall 
it happened.

At any rate, the above snippet has been introduced as testcase 'ValLub.java'. 
We'll have to keep an eye out and, next time, put more effort into 
double-checking the smallest snippet that is (supposed to!) be the minimum code 
for reproducing it.

Original comment by reini...@gmail.com on 29 Oct 2012 at 10:17