Friday, February 1, 2013

Re: Does GWT optimize inefficient code?

the first one: unlikely - the size might change in the loop
the second one is more likely

Am 01.02.2013 19:27, schrieb Joel Cairney:
> Dear forum,
>
> I've searched as hard as I can, but I haven't found any information on
> what specific developer practices GWTs compiler optimizations might
> optimize out. For instance:
>
> for(int i = 0; i < myList.size(); i++) {...}
>
> or in the presenter:
>
> getView().doAction();
>
> for every action, instead of:
>
> _view.doAction();
>
>
> Note that I'm not suggesting I plan to go through my code base and fix
> these, so please, please spare me the discussion on whether premature
> optimization is the root of all evil. I would just like my curiousity
> satisfied. Does GWT compiler change these code imperfections?
>
> -Joel
>
> --
> You received this message because you are subscribed to the Google
> Groups "Google Web Toolkit" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to google-web-toolkit+unsubscribe@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>


--

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment