On Tue, Oct 16, 2012 at 7:19 AM, Herwig Hochleitner <[email protected]>wrote:
> Certainly, such a simple optimization (omitting var reads in a statement > context) could live in the emitter. > The next stumbling block to a smaller clojurescript, however, is the > global-hierarchy var, which doesn't get removed by the closure compiler. To > shake that var, some closed world optimization could be utilized. I'd be > happy to work on that, but I need compilation units in order to do that. > I'm aware of this one as well. But again I think we can and should do a quick fix in the compiler for this. Either the user used multimethods or they did not. These kind of simple approaches may seem "hacky" but I think the benefit to users in terms of code size today outweighs those concerns - the discussed fixes would be quite simple to remove when a more general optimization strategy is in place. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en
