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.

Sign up for GitHub

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

Jump to bottom

Lexer can still allocate memory in the case of parsing strings with escape characters #103

Open

sungam3r opened this issue Jan 10, 2021 · 0 comments

Labels

Member

sungam3r commented Jan 10, 2021

No description provided.

sungam3r added the performance label

sungam3r mentioned this issue

Ensure October spec compliance before v8 release and publish release #206

Open

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