Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Investigate native JS implementation for ParseInt where permitted #1218

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
Open
flimzy opened this issue Jun 27, 2023 · 0 comments
Open

Investigate native JS implementation for ParseInt where permitted #1218

flimzy opened this issue Jun 27, 2023 · 0 comments
Labels
enhancement NeedsInvestigation
Milestone
Runtime performance

Comments

@flimzy
Copy link
Member

flimzy commented Jun 27, 2023

#1101 gained us some performance by using the native JS API for some string-to-int conversions. Now that #798 has been merged, we ought to experiment with using the native JS API for compatible calls to ParseInt, then fall back to the Go implementation where necessary.

See #1101 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement NeedsInvestigation
Projects
None yet
Milestone
Runtime performance
Development

Successfully merging a pull request may close this issue.

Use native JS API for ParseInt where possible gopherjs/gopherjs
2 participants
@nevkontakte @flimzy