Try/catch not tree-shaken if containing empty statement

[stephanedr]

• Rollup Version: 1.24.0
• Operating System (or Browser): Linux
• Node Version: 10.16.3

How Do We Reproduce?

With tryCatchDeoptimization=false.

try {
    ;
}
catch (e) {
}

This code is generated after plugin stripping code.

Expected Behavior

Completely removed.

Actual Behavior

Generates:

try {
}
catch (e) {
}

Workaround: run rollup a 2nd time to remove it.

[lukastaegert]

Oh sorry, I did not read properly, you already used the flag

[lukastaegert]

Good point, the logic was slightly tailored towards the tryCatchDeoptimization: true case. Now the false case will properly look for side-effects in #3166.