From @masak

<moritz_> rakudo​: rule w { . }; 'a' ~~ m/<w>/; for %($/<w>).kv {}
<p6eval> rakudo 50279c​: RESULT«Method 'HOW' not found for invocant of
class 'Iterator' [...]
* moritz_ found a bug
<masak> moritz_​: shall I send it in?
<moritz_> masak​: please do
* masak does

From @pmichaud

On Mon, Mar 02, 2009 at 08​:33​:16AM -0800, Carl Mäsak wrote​:

<moritz_> rakudo​: rule w { . }; 'a' ~~ m/<w>/; for %($/<w>).kv {}
<p6eval> rakudo 50279c​: RESULT«Method 'HOW' not found for invocant of
class 'Iterator' [...]

While I agree that the error message is likely incorrect -- I'm not
sure what the intent of the original code is here. Wouldn't %($/<w>)
be empty, since the rule doesn't have any named captures?

Pm

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

From @moritz

On Mon Mar 02 16​:26​:59 2009, pmichaud wrote​:

On Mon, Mar 02, 2009 at 08​:33​:16AM -0800, Carl Mäsak wrote​:

<moritz_> rakudo​: rule w { . }; 'a' ~~ m/<w>/; for %($/<w>).kv {}
<p6eval> rakudo 50279c​: RESULT«Method 'HOW' not found for invocant of
class 'Iterator' [...]

While I agree that the error message is likely incorrect -- I'm not
sure what the intent of the original code is here. Wouldn't %($/<w>)
be empty, since the rule doesn't have any named captures?

It does, and it actually works. The example is bogus; the example above
didn't produce any output, and thus p6eval wraps it with a (do { ...
}).perl.print block and executes it a second time, which is where the
error message comes from.

I have no idea what an empty for-loop is supposed to return (a Nil?
empty List? or can't it used as an expression at all?), so I can't
decide if that's really a bug.

Cheers,
Moritz

From @pmichaud

Rakudo now does the right thing with iterating the match object​:

  > 'a' ~~ /<alpha>/; for %($<alpha>) { }; say "done";
  done
  >

Assigning to moritz for spectesting.

Pm

From @moritz

%($something_matchy) now returns a proper Perl 6 hash (which is tested),
and we have enough tests for %hash.kv. So I'm closing this ticket
without explicit test coverage, but with confidence that there's enough
implicit coverage.

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