[perl #68578] [BUG] 'Callable &x' in a signature doesn't mean what Rakudo thinks it means

[Carl Mäsak]

# New Ticket Created by  "Carl Mäsak" 
# Please include the string:  [perl #68578]
# in the subject line of all future correspondence about this issue. 
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=68578 >


<jnthn> rakudo: sub foo( &x) { say "ok" }; foo({ say "lol" })
<p6eval> rakudo 0d4fe0: OUTPUT«ok␤»
<jnthn> rakudo: sub foo(Callable &x) { say "ok" }; foo({ say "lol" })
<p6eval> rakudo 0d4fe0: OUTPUT«ok␤»
<jnthn> wtf
<jnthn> rakudo: sub foo(&x) { }; say &foo.signature.perl;
<p6eval> rakudo 0d4fe0: OUTPUT«:(x)␤»
<masak> something wrong?
<jnthn> rakudo: sub foo(Callable &x) { }; say &foo.signature.perl;
<p6eval> rakudo 0d4fe0: OUTPUT«:(x where all(Callable))␤»
<jnthn> :-/
<masak> please state the nature of your medical emergency.
<jnthn> masak: Callable &x should mean I can only pass something that
does Callable[Callable]
* masak submits rakudobug
<jnthn> Damm, just when I think I've got something right.
<wolverian> is the type parameter the return type?
<jnthn> The type parameter indicates the return type constraint.