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

Optimize using function inlining #48

Open
wmertens opened this issue Sep 4, 2012 · 0 comments
Open

Optimize using function inlining #48

wmertens opened this issue Sep 4, 2012 · 0 comments

Comments

@wmertens
Copy link
Contributor

wmertens commented Sep 4, 2012

Putting this here for future reference:

There currently is an issue with the optimizer, it doesn't do exactly the same tag parsing as the regular code because it replaces the regular calls with equivalent code. The correct solution is to replace calls with the end result if the call is static, using function inlining.

I had a look at doing that but it's a bit too much to take on for me right now. UglifyJS doesn't seem to have something like that out of the box and it should really be done by it and not the coffeecup optimizer.

Closure can do it: https://developers.google.com/closure/compiler/docs/api-tutorial3#enable
Haven't tested that though.

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

No branches or pull requests

1 participant