Sonny,

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 abilities.

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?

Adam

2017-09-18 0:36 GMT+08:00 Sonny To <son.c.to@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@gmail.com> wrote:

2017-08-17 10:13 GMT+08:00 mikel evins <mevins@me.com>:

> On Aug 16, 2017, at 9:11 PM, Marc Feeley <feeley@iro.umontreal.ca> wrote:
>
> The JavaScript backend is being worked on actively this summer.  It is in much better shape than 6 months ago.  Currently we are working on implementing a tree shaker to reduce the size of generated code.

Nice!

Thanks,

--me

What's new with respect to the Javascript output now?

_______________________________________________
Gambit-list mailing list
Gambit-list@iro.umontreal.ca
https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list

_______________________________________________
Gambit-list mailing list
Gambit-list@iro.umontreal.ca
https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list