On Sat Jul 03 08:37:36 2010, masak wrote:
> <masak> rakudo: sub foo(Str) {}; foo 42
> <p6eval> rakudo 7017d2: OUTPUT�Nominal type check failed for parameter
> ''; expected Str but got Int in 'foo' at line 11
> * masak submits rakudobug
> 
> Ok, so the un-awesome aspect of this is the "for parameter ''" part.
> It should identify the parameter in some other way, perhaps by
> position. The important thing is that, when the routine contains
> several parameter constraints with no associated variable name, they
> be distinguishable somehow.

This seems sufficient awesome now:

21:58 < [Coke]> rakudo: sub foo(Str) {}; foo 42
21:58 <+p6eval> rakudo 29f5cf: OUTPUT«===SORRY!===␤CHECK FAILED:␤Calling 'foo' 
                will never work with argument types (int) (line 1)␤    
                Expected: :(Str )␤»

Closable with tests.

-- 
Will "Coke" Coleda

Reply via email to