The &quot;Vector m a&quot; means that it&#x27;s a vector (like a Python list) that can only be m elements long, and those elements can only be of type a.  E.g. &quot;Vector 3 Int&quot; will always be a Vector with three integers in it.  If you try to treat it like a vector of any other length it will refuse to compile (e.g. pass it to a function that requires that it have 4 or more elements).<p>The whole line is the type declaration for a function (app) that takes a Vector of length m, and a Vector of length n, and produces a Vector of length (m+n).  Which is to say, the compiler knows at compile time what length the resulting Vector will be, and will fail to compile if the function you&#x27;ve written doesn&#x27;t - provably - always meet that requirement.<p>From a Haskeller&#x27;s perspective it&#x27;s amazing because container types are famous loopholes for code that produces runtime errors.  For instance, if you call the &quot;head&quot; function (returns the first element) on an empty list it will halt the program at run time with an error, despite the fact that it passed the type check (because an empty list and a full one have the same type).<p>As someone who learned Haskell and subsequently have been writing a lot of Python, I keep a mental tally of how many of my bugs (some of which took ages to track down) would have been caught immediately by a type system like Haskell or Idris&#x27;.  I&#x27;d say it&#x27;s well over half.<p>In Haskell those kind of errors are drastically reduced, but a few still slip through.  Languages like Idris can catch even more of them, in a clever way, which is awesome.