http://gwt-code-reviews.appspot.com/1442807/diff/4001/dev/core/src/com/google/gwt/dev/jjs/ast/JProgram.java File dev/core/src/com/google/gwt/dev/jjs/ast/JProgram.java (right):
http://gwt-code-reviews.appspot.com/1442807/diff/4001/dev/core/src/com/google/gwt/dev/jjs/ast/JProgram.java#newcode1015 dev/core/src/com/google/gwt/dev/jjs/ast/JProgram.java:1015: public void setRunAsyncs(List<JRunAsync> runAsyncs) { Just curious, was thinking about this as I was looking at the other current Pruner patch. Is it possible for the set of runAsync fragments to decrease, say if a GWT.runAsync() call site gets pruned? Do we account for that possibility? Or do we always rescue all split-points regardless? (that's what I think I'm seeing). Not sure how often a developer introduces unreachable splitpoints (or relegates them as dead when not cleaning up legacy functionality). But it could be something to consider, here or as a separate patch. http://gwt-code-reviews.appspot.com/1442807/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
