Skip to content
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

Support quick normalization checks #1

Open
harendra-kumar opened this issue Mar 24, 2016 · 3 comments · May be fixed by #87
Open

Support quick normalization checks #1

harendra-kumar opened this issue Mar 24, 2016 · 3 comments · May be fixed by #87

Comments

@harendra-kumar
Copy link
Member

No description provided.

wismill added a commit to wismill/unicode-transforms that referenced this issue May 23, 2019
@jgm
Copy link

jgm commented Apr 18, 2021

This would be great. I'd have a use for this in unicode-collation; if we could quickly determine that the text is already normalized and avoid the expensive normalization step (which accounts for about 1/3 of my run time according to profiling and benchmarks), that would help us achieve parity with text-icu.

@harendra-kumar
Copy link
Member Author

We can do that, its just a matter of putting some time on it. In the meanwhile we can try to figure out how fast unicode-collation can go with the current impl itself. I guess there will be some avenues to optimize irrespective of this.

@jgm
Copy link

jgm commented Apr 20, 2021

If you have any suggestions for optimizing, I'd be glad to hear them.

@wismill wismill linked a pull request Jun 7, 2022 that will close this issue
3 tasks
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 a pull request may close this issue.

2 participants