…lines 1–12 unchanged (12 lines)
13 * Stephan Herrmann - Contributions for
14 * Bug 452788 - [1.8][compiler] Type not correctly inferred in lambda expression
15 *******************************************************************************/
16package org.eclipse.jdt.internal.compiler.ast;
17
18import org.eclipse.jdt.internal.compiler.lookup.BlockScope;
19import org.eclipse.jdt.internal.compiler.lookup.InferenceContext18;
20import org.eclipse.jdt.internal.compiler.lookup.InvocationSite;
21import org.eclipse.jdt.internal.compiler.lookup.MethodBinding;
22import org.eclipse.jdt.internal.compiler.lookup.PolyTypeBinding;
23import org.eclipse.jdt.internal.compiler.lookup.Scope;
24import org.eclipse.jdt.internal.compiler.lookup.TypeBinding;
25
…lines 26–60 unchanged (35 lines)
61 /* Resolution: A poly expression must be prepared to be resolved multiple times and should manage matters in a side effect free fashion.
62 Typically, in invocation contexts, there is an initial resolution, multiple tentative resolutions and then a final resolution against
63 the ultimate target type.
64 */
65 public TypeBinding resolveType(BlockScope blockScope);
66 // Resolve expression tentatively - should have no lingering side-effects that may impact final resolution !
67 public Expression resolveExpressionExpecting(TypeBinding targetType, Scope scope, InferenceContext18 inferenceContext);
68
69}