-
Notifications
You must be signed in to change notification settings - Fork 207
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
Investigate using regexpp Instead of regexp-to-ast #777
Comments
I am not sure migration would be worth the effort. |
Now that several new regExp features need to be supported (lookbehind/named capture groups) It could also be evaluated in terms of performance easily as there is a (minimal) cold start benchmark now. |
Had another quick look, This seems even more interesting to examine as:
|
Performance of regexpp seems very similar to regexp-to-ast
|
The regexpp does not seem to be well maintained at this time, perhaps the plans for swapping it out should be shelved. |
Actually it seems pretty active compared to regexp-to-ast. Latest release June 14, 2021 vs Dec 19, 2019. Also, and crucially, regexpp supports unicode escape sequences and groups. This is a must-have here in 2021! |
Hi @mattbishop I tried to recall what were my previous issue with regexpp
I'd still prefer to use a 3rd party library, but this means I need to find a way to patch it. |
It may be possible to combine https://www.npmjs.com/package/patch-package with "bundledDependencies" to resolve (patch-hack) regexpp |
Would it be hard to create a PR? I am assuming you have already forked
regexpp. If you haven't I can put one together.
…On Thu, Oct 7, 2021 at 12:30 PM Shahar Soel ***@***.***> wrote:
It may be possible to combine https://www.npmjs.com/package/patch-package
with "bundledDependencies" to resolve (patch-hack) regexpp
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#777 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACY3BOADTUJGYSDNZELKA3UFXYNXANCNFSM4FJQG3MQ>
.
|
I created one over a year ago... That is why I need some hack to apply the patch as a consumer 😄 |
Assuming an hack is possible, the bigger work would the integration of regexpp instead of regexp-to-ast |
I pinged the regexpp maintainer and asked them to merge your request. If
they don't then it might be easier to publish a different version with this
change, along with others in the PR list, to suit Chevrotain. You will
likely find other things that need attention too.
…On Thu, Oct 7, 2021 at 1:16 PM Shahar Soel ***@***.***> wrote:
Assuming an hack is possible, the bigger work would the integration of
regexpp instead of regexp-to-ast
I started this a while ago, to be honest I don't recall the status it is in
- https://github.com/Chevrotain/chevrotain/tree/regexpp
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#777 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACY3BLUKYT4OWR6E355EDLUFX52LANCNFSM4FJQG3MQ>
.
|
I am a little conflicted to be honest. On one hand it would be very nice to have a blackbox providing all the regexp parsing needs.
Maybe I should instead focus on updating regexp-to-ast to most modern regexp syntax. |
Well it is nicer to have control of such an important lib. If you move it into the monorepo then it can stay in sync easier. Is anyone outside of chevrotain using it? |
There are a handful of dependents. But they can still consume it if I move it to @chevrotain/regexp-to-ast package. anyhow I am closing this in favor of #1670 |
The text was updated successfully, but these errors were encountered: