adam.mlmb at gmail.com
Mon Sep 18 03:10:23 EDT 2017
Gambit has its own register of global variables, which it keeps in some JS
object. An external JS code tree shaker would not be able to distinguish
what can be removed and what cannot as they - as far as I am aware - not
introspect JS structures, but instead just look for unused
identifiers/functions and remove those. And also it would not be able to
remove what's not used.
So the whole way input code maps to JS code is beyond what JS code shaker's
However maybe my understanding of your JS tree shaker is not correct and
it's so incredibly smart that it can cut through also such intricate code.
What about you give it a try and let us know here?
2017-09-18 0:36 GMT+08:00 Sonny To <son.c.to at gmail.com>:
> Have you considered running the output through google closure compiler for
> the tree shaking? thats what clojurescript does
> On Sun, Sep 17, 2017 at 6:21 AM Adam <adam.mlmb at gmail.com> wrote:
>> 2017-08-17 10:13 GMT+08:00 mikel evins <mevins at me.com>:
>>> > On Aug 16, 2017, at 9:11 PM, Marc Feeley <feeley at iro.umontreal.ca>
>>> in much better shape than 6 months ago. Currently we are working on
>>> implementing a tree shaker to reduce the size of generated code.
>> Gambit-list mailing list
>> Gambit-list at iro.umontreal.ca
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gambit-list