Skip to content

get rid of usages of codepoints functions that are slow #43

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

Closed
wants to merge 2 commits into from

Conversation

justinwoo
Copy link
Collaborator

Sorry, this is all my fault. I forgot to try to purge all usages of CodePoints functions before and ran into this when one of my parsers became 100x slower.

@hdgarrood
Copy link
Contributor

I’m not sure this is necessarily how we should be going about addressing this; the CodePoints functions were set as the default ones for a reason. Someone should at least investigate to see if we can improve performance there before giving up on the CodePoints functions entirely.

@justinwoo
Copy link
Collaborator Author

What could be done to improve performance using them? I couldn't find a good solution other than to reimplement combinators entirely.

@justinwoo
Copy link
Collaborator Author

Other solution would be for us to write all over the README that this doesn't do anything outside of CodeUnits and anyone who wants a CodePoints solution should submit a PR that works with an array of CodePoints or something.

@justinwoo
Copy link
Collaborator Author

Updated the README here to say that this works with code units, not code points

@justinwoo
Copy link
Collaborator Author

Closing as there is #44 now

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

Successfully merging this pull request may close these issues.

2 participants