openide

BothVarargs.java

new inference: choose most specifics between 2 varargs methods

2014-03-12 10:16:12 +01:00

testdata: ensure overload resolution prefer correct one from methods with boxed types

2014-04-22 20:02:49 +02:00

DifferentParamsLength.java

lambda: highlight containing method ambiguity on method name: this avoids lots of lines of lambda body to be highlighted and it would show errors even if lambda body contains errors actually caused by the ambiguity on the parent level (IDEA-141580)

2015-06-18 17:54:23 +03:00

EnsureArgTypesAreNotCalculatedDuringOverload.java

new overload resolution: first check that collected methods are potentially compatible with args; for generic methods without specified type arguments this already means that they are applicable; for non generic methods (or raw method calls) expressions should be compatible with parameter types (formal parameter types = actual types as substitutor is known) (IDEA-147798)

2015-11-20 18:22:02 +01:00

FunctionalTypeComparisonWhenMethodsAreNotGeneric.java

most specific check: ensure that functional types are specifically checked when method is not generics (IDEA-136287)

2015-02-11 19:05:41 +01:00

IDEA121884.java

testdata for IDEA-121884

2014-03-12 10:19:22 +01:00

IDEA121999.java

testdata for IDEA-121999

2014-03-12 10:19:45 +01:00

IDEA123352.java

ambiguity (IDEA-123352)

2014-04-03 17:15:53 +02:00

IDEA125855.java

most specific: do not start java 8 algorithm for provided type args (IDEA-125855)

2014-06-03 18:41:27 +04:00

IDEA127584.java

new inference: no substitution during most specific inference by means of new spec (IDEA-127584)

2014-07-21 17:56:20 +02:00

IncompatibleSiteSubstitutionBounds.java

overload resolution: reject more specific inference contradicting site substitution

2015-08-26 12:08:47 +03:00

IncompleteMethodInInterface.java

lambda: highlight containing method ambiguity on method name: this avoids lots of lines of lambda body to be highlighted and it would show errors even if lambda body contains errors actually caused by the ambiguity on the parent level (IDEA-141580)

2015-06-18 17:54:23 +03:00

InferSpecificForGenericMethodWhenCallProvidesExplicitTypeArguments.java

most specific: infer specific if method is generic even if type arguments are explicitly provided

2015-02-13 18:54:03 +01:00

JDK8034223.java

isApplicability check based on pertinentToApplicability

2015-11-30 15:11:41 +01:00

JDK8042508.java

testdata for JDK-8042508

2014-05-07 12:29:28 +04:00

MostSpecificByReturnType.java

new overload resolution: covariant comparison of return types

2014-04-22 20:02:33 +02:00

MostSpecificForSameFunctionalTypes.java

new inference: most specific with same functional interface presence

2014-03-12 10:17:33 +01:00

NestedLambdaSpecifics.java

…

NestedVarargs.java

new inference: nested varargs

2014-03-12 10:17:10 +01:00

NoReturnTypeResolutionForThrownException.java

new inference: most specific check according to spec, fixed testdata after JDK-8043734

2014-09-04 13:45:03 +04:00

RelatedSAMErasures.java

lambda: highlight containing method ambiguity on method name: this avoids lots of lines of lambda body to be highlighted and it would show errors even if lambda body contains errors actually caused by the ambiguity on the parent level (IDEA-141580)

2015-06-18 17:54:23 +03:00

SuperMethodsInExactCheck.java

method refs: is exact should check super methods for this/super qualifiers only (IDEA-124507)

2014-04-28 15:12:44 +02:00

TargetTypeParameter.java

isApplicability check based on pertinentToApplicability

2015-11-30 15:11:41 +01:00

VarargsSpecificsDuringMethodReferenceResolve.java

method references: compare number of arguments for non-vararg applicability only (IDEA-132708)

2014-11-11 12:03:06 +01:00

VoidConflict.java

…