Skip to content

Use native JS API for ParseInt where possible #1221

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
Closed

Conversation

flimzy
Copy link
Member

@flimzy flimzy commented Jul 14, 2023

WIP PR to fix #1218

@flimzy flimzy changed the title Add GopherJS wrapper/stub around ParseInt Use native JS API for ParseInt where possible Jul 14, 2023
@github-actions

This comment has been minimized.

@github-actions
Copy link

Reference app: jQuery TodoMVC (acf500a6c32a83d8c4582d967b09a65febf0e120)

BRANCH ORIGINAL MINIFIED COMPRESSED (GZIP)
Pull request (ParseInt) 2,947,277 bytes 1,933,209 bytes 382,994 bytes
Target branch (master) 0.02% increase (560 bytes) 0.01% increase (214 bytes) 0.02% increase (76 bytes)

#outputSize

@flimzy flimzy closed this Jul 28, 2023
@flimzy flimzy deleted the ParseInt branch July 28, 2023 14:14
@nevkontakte
Copy link
Member

I'm curious why did you decide to close this? Did it not yield a meaningful improvement?

@flimzy
Copy link
Member Author

flimzy commented Jul 30, 2023

There are many corner cases that make it not as easy as I first expected. So while I intend to get back to it, it didn't seem right to lave this virtually empty PR open in the meantime.

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 this pull request may close these issues.

Investigate native JS implementation for ParseInt where permitted
2 participants