Java 8 language spec flaw/bug
davmac at bluej.org
Fri Aug 22 19:20:25 UTC 2014
On 22/08/14 17:56, Maurizio Cimadamore wrote:
> Well, if you look at Dan's eval of 8044053, he explains that the
> conditional is missing the same subtle check that has been applied for
> nested method calls - i.e. a reference conditional is always a poly
> conditional - it's never type-checked bottom up; on the other hand,
> for nested method calls there is some extra analysis to prevent
> constraint propagation and to allow for more compatibility. I think
> that, in the case of conditionals, there's a design tension between
> being able to define a granular enough classification (poly vs.
> standalone) that will allow 'reasonable' code to compile vs. defining
> a classification analysis that's easy to spot when you read the code.
Ok, got it (I think). Thanks for your time, this has been very helpful
for me in understanding the type inference process generally.
More information about the lambda-dev