Closed GoogleCodeExporter closed 9 years ago
Original comment by Nicholas.J.Santos
on 18 Dec 2013 at 9:57
We could also fix this particular code snippet by allowing FunctionInjector to
inline simple 'new' calls, but i think solving the more general problem could
open up possibilities elsewhere.
Original comment by Nicholas.J.Santos
on 18 Dec 2013 at 11:35
I've thought about this a number of time. Previously, we didn't do it because
we wanted smart name removal to take advantage of it but we run that later now
too.
Running just before the first smart name removal (after the first dead code
run) might be sufficient. doing local dead code removal before disambiguate
properties might be helpful too.
Original comment by concavel...@gmail.com
on 19 Dec 2013 at 7:43
Issue tracking has been migrated to github. Please make any further comments on
this issue through https://github.com/google/closure-compiler/issues
Original comment by blic...@google.com
on 1 May 2014 at 6:31
Original comment by blic...@google.com
on 1 May 2014 at 6:34
Original issue reported on code.google.com by
Nicholas.J.Santos
on 18 Dec 2013 at 9:56