Do not apply negate_iife optimization to new expression

[kzc]

Potential fix for #1073

[rvanvelzen]

I think just checking for AST_New is enough? The cause here is that AST_New extends from AST_Call, but it shouldn't get the same treatment here.

[kzc]

I think it's a problem that's specific to ECMAscript new syntax. Do you have a counter case involving a javascript call that fails in a major browser or node?

[rvanvelzen]

Sorry, I may have been a bit unclear. The check can be simplified to just:

if (node instanceof AST_New) {
    return node;
}

... because even though this case only fails when node.expression is a function, new doesn't need this optimization anyway.

[kzc]

@rvanvelzen Good point. I wasn't sure such a fix would allow for nested IIFE's, but it does. PR revised.

[rvanvelzen]

Awesome, thanks!