-
-
Notifications
You must be signed in to change notification settings - Fork 415
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 regress
fixes #478
#686
Conversation
- TODO: Fix methods using capture groups - Hopefully everything still works with the refactor other than capture groups
@Razican was wondering whether you had any idea on how to refactor the capture groups that are failing here. Specifically in |
I've managed to make it compile, but the tests are failing, I think the creation of the Regex struct needs to change. My work is here: https://github.com/RageKnify/boa/tree/regress |
I would need to give it a look, but I don't think I will have the time this week :/ |
Test: Improve string::tests::replace_with_function and fix minor typo Can be improved once ridiculousfish/regress#7 is closed
@neeldug I believe my branch will finish the PR, it passes |
I don’t mind @RageKnify, I’ll rebase it myself since that should be easier. |
Codecov Report
@@ Coverage Diff @@
## master #686 +/- ##
==========================================
- Coverage 73.17% 71.69% -1.49%
==========================================
Files 194 199 +5
Lines 14029 13859 -170
==========================================
- Hits 10266 9936 -330
- Misses 3763 3923 +160
Continue to review full report at Codecov.
|
Match::groups simplifies some code.
- TODO: Fix methods using capture groups - Hopefully everything still works with the refactor other than capture groups
Test: Improve string::tests::replace_with_function and fix minor typo Can be improved once ridiculousfish/regress#7 is closed
Match::groups simplifies some code.
Ran a rebase for benchmarking to run |
Here are the benchmarks you can access this by looking at the benchmark CI log, There seems to be a really big boost in RegExp performance!
|
Why are there old commit changes showing? |
I ran a rebase since the criterion versions were mismatched causing benchmarking to fail |
strange , I think changing the merge base to a different one and back to master may fix this |
I think creating a new branch from |
@RageKnify it seems to be sorted now though? |
GitHub seems to think we're merging 11 |
This shouldn't be a problem since we always squash and merge the PRs into master so, on the master branch all the changes will be represented by one commit ( |
@neeldug resolve the conflicts when you can please |
@RageKnify accidentally deleted fork while this PR was active, have created a new PR with all of the previous commits at #774 |
This Pull Request fixes/closes #478.
It changes the following: