Skip to content

Conversation

zherczeg
Copy link
Collaborator

@zherczeg zherczeg commented Nov 9, 2023

I have started working on vreverse. Unfortunately the task is very hard, because it adds another layer to the already complex bracket/assertion matching. Each new layer kind of duplicates the complexity, so I have no idea how many bugs I introduce with this patch. To tell the truth it was a long time ago when I developed the original code, and forgot many things since then.

The tests are passing now, although @PhilipHazel mentioned the vreverse tests are disabled for jit. I didn't see anything which disables them. Is there something I miss?

The patch also contains some unicode fixes, they can be moved to another patch if needed.

@PhilipHazel
Copy link
Collaborator

There was no need to cut out JIT for vreverse tests because of the automatic fallback to the interpreter. The cut out tests are for the changes to \w and [:xdigit:]. I will merge and run tests on this patch shortly. That then leaves only the \w and [:xdigit:] changes that need an update to JIT.

@PhilipHazel PhilipHazel merged commit 494e765 into master Nov 9, 2023
@PhilipHazel
Copy link
Collaborator

As you were. I see that this patch also contains the updates for \w and [:xdigit:]. Thanks.

@zherczeg zherczeg deleted the vreverse branch November 9, 2023 18:06
@zherczeg
Copy link
Collaborator Author

zherczeg commented Nov 9, 2023

I am thinking about optimizing the ucp support further. Btw I added the support here because I got all kinds of assertion failures in debug without them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants