-
Notifications
You must be signed in to change notification settings - Fork 0
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
Implement lookaround #1
Milestone
Comments
It would be great to propagate raku / perl6 regexes to other languages and Rust seems good for the beginning... |
I have not worked on this for a very long time and currently have no plans to currently. If someone decides to start working on this, I can add them as a collaborator or something similar so they can start doing cool things with it. |
Yep it would be nice to have it, but I also could not find time for such project currently...
Pozdrawiam,
Jakub A. Gramsz
…________________________________
From: mdinger ***@***.***>
Sent: Friday, December 10, 2021 11:37:40 PM
To: mdinger/rules ***@***.***>
Cc: Jakub A. G. ***@***.***>; Comment ***@***.***>
Subject: Re: [mdinger/rules] Implement lookaround (#1)
I have not worked on this for a very long time and currently have no plans to currently. If someone decides to start working on this, I can add them as a collaborator or something similar so they can start doing cool things with it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#1 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABNIB5JZOLDOFCUAEVNVDLDUQJ6LJANCNFSM4BPYSDPQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
foo <?after bar>
matchesfoo
infoobar
foo <!after bar>
matchesfoo
infoobaz
<?before foo> bar
matchesbar
infoobar
<!before foo> bar
matchesbar
insushibar
An example with both:
<?before foo> bar <?after baz>
matchesbar
infoobarbaz
This is different from Perl 6 as noted in perl_changes and is subject to change. I'll need to get experience using it and then compare. Perl 6 may have gotten it correct but I'm not sure or convinced. Granted, I don't think deviating from Perl 6 shouldn't be taken lightly.
I have a PR for this but it doesn't work correctly and I have to do a major revision. Not sure when I'll get to it.
The text was updated successfully, but these errors were encountered: