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
Parse error on a way of writing ranges in infix:<**> quantifiers that probably should work in Rakudo #3479
Comments
From @masak<psch> m: /a ** 1 ..2/ # this does confuse me. It's not clear to me whether the above should just work (probably) or |
From @peschwaOn Sun Aug 10 09:00:08 2014, masak wrote:
It should not work. 21:33 <psch> std: /m ** 1 ..1/ X::Syntax::Regex::SpacesInBareRange has recently been created, but the patch which did so wasn't submitted for merging before changes to how the range is parsed broke an assumption between P6Regex::Grammar and P6Regex::Actions. A PR for NQP exists at [0]. [0] Raku/nqp#174 |
The RT System itself - Status changed from 'new' to 'open' |
From @peschwaAm So 10. Aug 2014, 12:40:20, peschwa@gmail.com schrieb:
The mentioned NQP-PR has been merged, a test has been added and corrected in roast commits 59436af1 and a0a80b76. |
From @usev6Since the test in S32-exceptions/misc.t passes for Rakudo on Moar, Parrot and JVM, I'm closing this ticket. |
1 similar comment
From @usev6Since the test in S32-exceptions/misc.t passes for Rakudo on Moar, Parrot and JVM, I'm closing this ticket. |
@usev6 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#122502 (status was 'resolved')
Searchable as RT122502$
The text was updated successfully, but these errors were encountered: