hg: lambda/lambda/langtools: 8016177: structural most specific and stuckness; ...

[Paul Benedict]

If I may ask, what is the "stuckness" that's been introduced in the
refactoring? What is stuck and why? I saw the term in the previous commit
too and wonder what it is referring to.


On Fri, Jul 26, 2013 at 6:47 AM, <maurizio.cimadamore at oracle.com> wrote:

> Changeset: 00274133b7d2
> Author:    mcimadamore
> Date:      2013-07-26 12:46 +0100
> URL:
> http://hg.openjdk.java.net/lambda/lambda/langtools/rev/00274133b7d2
>
> 8016177: structural most specific and stuckness
> 8016178: Order of unsticking functional expressions
>
> Refined rules for structural most specific for lambda/method references
> after recent changes.
>
> ! src/share/classes/com/sun/tools/javac/comp/DeferredAttr.java
> ! src/share/classes/com/sun/tools/javac/comp/Resolve.java
> ! src/share/classes/com/sun/tools/javac/tree/JCTree.java
> ! test/tools/javac/diags/examples/IncompatibleArgTypesInMethodRef.java
> ! test/tools/javac/lambda/8016177/T8016177c.java
> + test/tools/javac/lambda/8016177/T8016177c.out
> ! test/tools/javac/lambda/methodReference/SamConversionComboTest.java
>
>
>


-- 
Cheers,
Paul