-
Notifications
You must be signed in to change notification settings - Fork 216
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
Json-ifying string with newlines in it creates invalid JSON #492
Comments
We ran into another similar issue due to special characters not escaped in |
Hi @yalinhuang, looking into this one. |
Only process a single character at a time - Processing 4 at at a time has more repeatable timing but on average is slower. Processing an unescaped string can be faster than the original method of find/find.
Properly handle UTF-16
No description provided.
The text was updated successfully, but these errors were encountered: