Hey guys, I ran into some issues because my previous patch was lazy. I was avoiding optimizing ALL calls to runAsync.onSuccess() in TypeTightener and MethodCallTightener. Turns out that some projects *depending* on those calls being optimized. So I went back and added a way to unambiguously mark a particular call "don't optimize this!". I went the enum route to avoid adding yet another boolean flag that would increase net memory consumption of JMethodCall.
http://gwt-code-reviews.appspot.com/1442807/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
