René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"NewableFunction not working as intended","articleBody":"There is little info about `NewableFunction` except for the meeting notes in #27102 and the pr #27028.\r\n\r\nAs far as I understand the comments there, **a  `NewableFunction` should be \"callable\" with `new Foo(...)`, right?** Or do we have to stick with `apply(...)`/`call(...)`?\r\n\r\nExample:\r\n\r\n```typescript\r\nclass Foo {}\r\n\r\nfunction doSomething(clazz: NewableFunction) {\r\n  new clazz();\r\n  // This expression is not constructable.\r\n  //   Type 'NewableFunction' has no construct signatures\r\n}\r\n\r\n\r\n\r\ndoSomething(Foo); // passes but would fail with \"normal functions\" aka. CallableFunction\r\n```\r\n\r\n\r\n**Question about workaround:**\r\n\r\nIf `NewableFunction` works as desired should we stick with  `new Function.prototype.bind.call(clazz, undefined);` or should we define our own \"`ConstructableFunction`\" (a lot of people suggest this and [even angular did it](https://github.com/angular/angular/blob/6.1.6/packages/core/src/type.ts#L25)):\r\n\r\neg.\r\n\r\n```typescript\r\nexport interface ConstructableFunction extends NewableFunction {\r\n  new(...args: any[]): any\r\n}\r\n```\r\n\r\n","author":{"url":"https://github.com/rajmondx","@type":"Person","name":"rajmondx"},"datePublished":"2021-05-30T04:11:43.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/44337/TypeScript/issues/44337"}