Make unimatch test fail for the right reason

unimatch should always be called with at least 2 parameters as a sub,
or one parameter as a method.

S15-unicode-information/unimatch-general.t

@@ -10,10 +10,10 @@ plan 224;
 
 is unimatch("",'Nd'), Nil, "unimatch an empty string yields Nil";
 is "".unimatch('Nd'), Nil, "''.unimatch yields Nil";
-throws-like "unimatch Str", X::Multi::NoMatch, 'cannot call unimatch with a Str';
-throws-like "Str.unimatch", X::Multi::NoMatch, 'cannot call unimatch with a Str';
-throws-like "unimatch Int", X::TypeCheck::Argument, 'cannot call unimatch with a Int';
-throws-like "Int.unimatch", X::Multi::NoMatch, 'cannot call unimatch with a Int';
+throws-like "unimatch Str, 'Latin'", X::Multi::NoMatch, 'cannot call unimatch with a Str';
+throws-like "Str.unimatch: 'Latin'", X::Multi::NoMatch, 'cannot call unimatch with a Str';
+throws-like "unimatch Int, 'Latin'", X::Multi::NoMatch, 'cannot call unimatch with a Int';
+throws-like "Int.unimatch: 'Latin'", X::Multi::NoMatch, 'cannot call unimatch with a Int';
 
 nok unimatch(0x29, 'Nd'), "0x29 is not Nd";
 ok unimatch(0x30, 'Nd'), "0x30 is Nd";