Disallow new with empty parens

The rule can be implemented as one of the following:

• an option in new-parens rule
• an option in no-extra-parens rule
• a separate rule

When does this rule warn? Please describe and show example code:

var p = new Person(); // error
var p = new Person; // correct
var name = new Person().getName(); // optionally correct

Is this rule preventing an error or is it stylistic?

Stylistic

Why is this rule a candidate for inclusion instead of creating a custom rule?

It is generic

Are you willing to create the rule yourself?

Yes

[btmills]

@platinumazure good catch, that’s quite the wrench. Let’s see… Based on the cases demonstrated below, it looks like we’ll need either a tri-state or an option on the “never”. I agree with @epoberezkin that immediate property access is pretty ugly, so maybe there’s a way to support that too.

/* 1 */ new Class()
/* 2 */ new Class.staticPropertyReturningConstructor()
/* 3 */ new Class().instanceProperty
/* 4 */ new Class().instanceMethod()
/* 5 */ new Class
/* 6 */ new Class.staticPropertyReturningConstructor
/* 7 */ (new Class).instanceProperty
/* 8 */ (new Class).instanceMethod()

So what if we started off with “always” (1-4 valid) and “never” (5-8 valid). Then, later, if someone requests an option that makes 3-6 valid, we could add a third state, making it “always”/“never”/“chained” or something like that.

[btmills]

What about adding an “always” (default) / “never” mode to new-parens?