Issue a more useful error when attempting to construct non-newable type

Inspired from http://stackoverflow.com/questions/24923772/raphael-with-typescript-call-signatures-used-in-a-new-expression-must-have-a

interface NotNewable {
    (n: number): string;
}

var n: NotNewable;
var t = new n(10);

New compiler says

Only a void function can be called with the ‘new’ keyword

Old compiler says

Call signatures used in a ‘new’ expression must have a ‘void’ return type.

This error is written as if it’s the .d.ts author’s fault, not the calling code’s fault. A more useful error would be something like “Specified type does not have a signature that can be called with ‘new’”

[Andarist]

The current error for this kind of thing is:

‘new’ expression, whose target lacks a construct signature, implicitly has an ‘any’ type.(7009)

which seems to satisfy the specified goal of this ticket:

This error is written as if it’s the .d.ts author’s fault, not the calling code’s fault. A more useful error would be something like “Specified type does not have a signature that can be called with ‘new’”

cc @RyanCavanaugh

[Spongman]

I’m running into this error a lot when checking legacy javascript code. The obscurity of this message might have made sense back when --noImplicitAny was a hidden compiler flag. howadays, not so much…