http://codereview.appspot.com/2241042/diff/1/src/com/google/caja/parser/quasiliteral/opt/ArrayIndexOptimization.java File src/com/google/caja/parser/quasiliteral/opt/ArrayIndexOptimization.java (right):
http://codereview.appspot.com/2241042/diff/1/src/com/google/caja/parser/quasiliteral/opt/ArrayIndexOptimization.java#newcode40 src/com/google/caja/parser/quasiliteral/opt/ArrayIndexOptimization.java:40: * <p>The CajitaRewriter will optimize reads of properties where the index On 2010/10/07 21:05:11, jasvir wrote:
Update to reference ES53 (which also does this)
Done. http://codereview.appspot.com/2241042/diff/1/src/com/google/caja/plugin/PipelineMaker.java File src/com/google/caja/plugin/PipelineMaker.java (right): http://codereview.appspot.com/2241042/diff/1/src/com/google/caja/plugin/PipelineMaker.java#newcode236 src/com/google/caja/plugin/PipelineMaker.java:236: out.add(new OptimizeJavascriptStage()); On 2010/10/07 21:05:11, jasvir wrote:
Can we get no-optimize as an option?
How would that work? And who would be a client of this? It doesn't seem like there is any identifiable property of the input JS that we would hinge this on. http://codereview.appspot.com/2241042/
