Open NotWearingPants opened 4 years ago
Closure Compiler with advanced optimizations fails to optimize the expression {a:0}.a to 0 in some cases.
{a:0}.a
0
When running:
echo console.log({a:0}.a) | java -jar closure-compiler-v20191027.jar -O ADVANCED
I get console.log({a:0}.a);
console.log({a:0}.a);
but when running:
echo console.log({a:0}.a===0) | java -jar closure-compiler-v20191027.jar -O ADVANCED
I get console.log(!0);.
console.log(!0);
It seems that the compiler knows that {a:0}.a can be reduced to 0, but doesn't always do it for no apparent reason.
Internal issue created: b/144415023.
Closure Compiler with advanced optimizations fails to optimize the expression
{a:0}.a
to0
in some cases.When running:
I get
console.log({a:0}.a);
but when running:
I get
console.log(!0);
.It seems that the compiler knows that
{a:0}.a
can be reduced to0
, but doesn't always do it for no apparent reason.