[flow][match] Fix match refinement of arrays with tuple views

Summary:
One day natural inference will mean we don't need to think about this, but until then we need to handle it.

Array literals initialized with some values act as a tuple. Handle them like we handle tuples.

Changelog: [internal]

Reviewed By: SamChou19815

Differential Revision: D67778713

fbshipit-source-id: a2b7bad3c8a02874027f82e2712cf797adc19275

src/typing/type_filter.ml

@@ -599,7 +599,12 @@ let not_array t =
 
 let array_length ~sense ~op ~n t =
   match t with
-  | DefT (_, ArrT (TupleAT { arity = (num_req, num_total); inexact; _ })) ->
+  | DefT (_, ArrT (TupleAT { arity = (num_req, num_total); inexact; _ }))
+  | DefT
+      ( _,
+        ArrT
+          (ArrayAT { tuple_view = Some (TupleView { arity = (num_req, num_total); inexact; _ }); _ })
+      ) ->
     (* `None` represents "maybe" a match *)
     let matches =
       match op with

tests/match/patterns.js

@@ -160,3 +160,12 @@
     _: 0,
   };
 }
+
+// Array pattern applied to array literal
+{
+  const x = [1, 'foo'];
+
+  const out = match (x) {
+    [_, const b]: b as string, // OK
+  };
+}