Allow augmentation of the async function prototype

Search Terms

AsyncFunction

Suggestion

In JavaScript, We can get constructor of async function via

const AsyncFunction= (async()=>{}).constructor;

And we can do something interesting with it's prototype:

AsyncFunction.prototype.callConcurrently = async function (concurrency,...args){
    return Promise.all(Array(concurrency).fill(this).map(f=>f(...args)));
}

Then we can do

const af = async ()=>{};
af.callConcurrently(6, 'foo', 'bar');

But in TypeScript, we have no AsyncFunction interface to do the same thing.

We can add an AsyncFunction interface extends Function and let all functions start with async keyword implement it. And add an AsyncFunctionConstructor interface let (async ()=>{}).constructor implements it. The mode is now new but just like GeneratorFunction and AsyncGeneratorFunction.

Use Cases and Example

interface AsyncFunction
{
    callConcurrently(concurrency:Number, ...args:any[]):Promise<any[]>;
}

(async()=>{}).constructor.prototype.callConcurrently = async function (concurrency, ...args){
    return Promise.all(Array(concurrency).fill(this).map(f=>f(...args)));
}

const af = async ()=>{};
af.callConcurrently(6, 'foo', 'bar');

Maybe Breaking Change

Currently async()=>3 and ()=>Promise.resolve(3) has the same type in TypeScript.
This proposal will make them different.
They are different in ECMAScript actually. See https://tc39.es/ecmascript-asyncawait/#async-function-constructor . So this breaking change actually fill the gap between TypeScript and ECMAScript.

Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
• This feature would agree with the rest of TypeScript's Design Goals 6
• This feature would agree with the rest of TypeScript's Design Goals 11.

Das Issue nennt keine Repository-Dateien oder Tests; beginne damit, die vorgeschlagenen AsyncFunction- und AsyncFunctionConstructor-Schnittstellen zusammen mit der verlinkten ECMAScript async-function-constructor-Spezifikation zu prüfen. Kläre die Kompatibilitätsgrenze zwischen async functions und Funktionen, die Promises zurückgeben; die Aufgabe ist abgeschlossen, wenn ein abgestimmtes Design für die Auswirkungen der breaking-change und das daraus resultierende TypeScript-Verhalten vorliegt.