Results 71 comments of Matthew Robb

@domenic From my understanding of the wiki, modules export immutable bindings. If I understand you correctly above, calling a shared export that mutates a binding SHOULD be reflected in imported...

I really wish there were some proposed API's to support grokkability of es6 modules. For example if modules create a frozen object of getters then that would practically look something...

That my be the culprit although honestly it's a big improvement over the simple traverse being used in some other scripts. I want to focus on getting the core features...

I am actively working on rewriting a lot of stuff with the tree building/visiting/traversing. I imagine we will see some performance improvements when all is said and done. My last...

OH! - Also you may want to look in to the performance implications of using getters. If we're returning a reference then I don't see the harm in storing that...

One more thing, can you integrate the benchmark setup you are using into the project?

I tried to pull your branch but it's missing ./timer module

Ah, the compiled file isn't in the repo

Try pulling this and see what results you get as far as speed improvements, My results with your timing branch seemed pretty positive: https://github.com/matthewrobb/six/tree/optimize

Went from 0.055861514 on the first compile pass to 0.038018141