New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
duplicate keys in .gist in Match of regex which backtracked in Rakudo #3074
Comments
From @masak<p6eval> rakudo 99e27f: OUTPUT«「/foo/bar/baz/」 dirname => The .gist output is bizarre. There should never be duplicate keys in a |
From @pmichaudOn Thu, Apr 04, 2013 at 02:09:36PM -0700, Carl Mäsak wrote:
The "gist" method uses ".caps" for the match output, so I suspect Duplicate keys can appear in the .caps stream. Pm |
The RT System itself - Status changed from 'new' to 'open' |
From @usev6There is no longer a duplicate key in the .gist output: $ perl6-m -e "say ('/foo/bar/baz/' ~~ m/^ I added a test to S02-names-vars/list_array_perl.t (couldn't find a better place) with the following commit: Raku/roast@9acc51a8d9 Please note: All of the above is under the assumption that the originial command (which is missing from the IRC log) was: r: say ('/foo/bar/baz/' ~~ m/^ If I misinterpreted the problem, please reopen the ticket. |
1 similar comment
From @usev6There is no longer a duplicate key in the .gist output: $ perl6-m -e "say ('/foo/bar/baz/' ~~ m/^ I added a test to S02-names-vars/list_array_perl.t (couldn't find a better place) with the following commit: Raku/roast@9acc51a8d9 Please note: All of the above is under the assumption that the originial command (which is missing from the IRC log) was: r: say ('/foo/bar/baz/' ~~ m/^ If I misinterpreted the problem, please reopen the ticket. |
@usev6 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#117481 (status was 'resolved')
Searchable as RT117481$
The text was updated successfully, but these errors were encountered: