From @masak

<masak> rakudo​: sub foo(​:$) {}; say &foo.signature.perl
<p6eval> rakudo c8181a​: OUTPUT«​:(Any $?)␤»
<moritz_> that's wrong :-)
<masak> why?
<moritz_> it's not a positional
<masak> oh, right.
* masak submits rakudobug
<Matt-W> but it should be a named optional
<Matt-W> :$?
<moritz_> right
<masak> rakudo​: sub foo(​:$a) {}; say &foo.signature.perl
<p6eval> rakudo c8181a​: OUTPUT«​:(Any :$a?)␤»
<masak> it gets that one right.

From @jnthn

On Wed Sep 30 06​:12​:28 2009, masak wrote​:

<masak> rakudo​: sub foo(​:$) {}; say &foo.signature.perl
<p6eval> rakudo c8181a​: OUTPUT«​:(Any $?)␤»
<moritz_> that's wrong :-)
<masak> why?
<moritz_> it's not a positional
<masak> oh, right.
* masak submits rakudobug
Now it shows up looking like a named parameter. You can also flatten a
hash with an empty string key in the arguments list to call such a sub! :-)

Given to moritz++ to see if he thinks spectesting this craziness is
worthwhile. ;-)

Jonathan

The RT System itself - Status changed from 'new' to 'open'

From @moritz

Tested in t/spec/S06-signature/introspection.t.

@moritz - Status changed from 'open' to 'resolved'

From @masak

<masak> r​: sub foo(​:$) {}; say &foo.signature.perl
<p6eval> ..rakudo 34e8d4​: OUTPUT«​:()␤»
* masak re-opens https://rt-archive.perl.org/perl6/Ticket/Display.html?id=69492

It's supposed to say something like '​:(​:$)'. Re-opening ticket.

@masak - Status changed from 'resolved' to 'open'

From @ShimmerFairy

  <lue> r​: sub foo(​:$) {}; say &foo.signature.perl
  <camelia> rakudo-parrot 20193f, rakudo-jvm 20193f, rakudo-moar 20193f​: OUTPUT«​:(Any :($))␤»

And once again it's fixed. Your serve :) .

From @peschwa

Am Do 13. Mär 2014, 19​:23​:15, lue schrieb​:

<lue> r​: sub foo(​:$) {}; say &foo.signature.perl
<camelia> rakudo-parrot 20193f, rakudo-jvm 20193f, rakudo-moar 20193f​:
OUTPUT«​:(Any :($))␤»

And once again it's fixed. Your serve :) .

Narrowed down the test for this issue in roast commit a3db7d2.

From @usev6

The test in S06-signature/introspection.t is passing (for quite a while, I guess). I'm closing this ticket now.

@usev6 - Status changed from 'open' to 'resolved'