Fix type test warning involving applied types

Previously, the check relied used `maximizeType`, which means that
depending on which bound got picked by type inference, the check might
fail. Instead, we only need to check if there is a possible constraint
solution by making sure both subtype tests return true.

I'm not sure if this is always a safe type test, but it at least avoids
spurious warnings. This is necessary to bootstrap dotty after the
previous commit which added a `dealias` to `recur`, this probably means that there
are other situations where `recur` is missing checks.

Author: smarter

compiler/src/dotty/tools/dotc/transform/TypeTestsCasts.scala

@@ -105,12 +105,7 @@ object TypeTestsCasts {
       debug.println("P1 : " + P1.show)
       debug.println("X : " + X.show)
 
-      P1 <:< X       // constraint P1
-
-      // use fromScala2x to avoid generating pattern bound symbols
-      maximizeType(P1, span, fromScala2x = true)
-
-      val res = P1 <:< P
+      val res = (P1 <:< X) && (P1 <:< P)
       debug.println("P1 : " + P1.show)
       debug.println("P1 <:< P = " + res)
 

tests/pos-special/fatal-warnings/patmat-applied.scala

@@ -0,0 +1,9 @@
+class A[-T]
+class B[T] extends A[T]
+
+object Test {
+  def foo(x: A[Null]) = x match {
+    case x: B[Null] =>
+    case _ =>
+  }
+}