Naveen Chawla

`await` is the correct ES-based syntax for the result of a resolved promise as an expression. e.g. in TypeScript/Javascript it's (already supported in Chrome/Firefox): `const name : string = (await...

Explanation [here](https://github.com/TheNavigateur/proposal-pipeline-operator-for-function-composition#why-treat-asyncfunction-generatorfunction-and-asyncgeneratorfunction-differently-than-their-promiseiterator-returning-function-equivalents-they-are-the-same-in-all-other-contexts). It's essentially centered on the way the function is semantically declared. Since these are concrete semantic constructs within JavaScript itself, it makes sense to honor their declared semantics...

One is an `AsyncFunction`, and the other is a `GeneratorFunction`. When using either in a composition, due to the way its "output" is declared, I expect that declared output to...

I believe the advantages far outweigh the disadvantages. I don't believe it's "magic" in light of how the functions are declared. It's only magic if you have to insist that...

By _semantic_, I mean a function's declared output value. As you probably already know, an async function is declared to return its promised value (this probably goes without saying): ```js...

@tabatkins I am precisely arguing that there should be a departure from that resolution, for the reasons stated. It has to be that the advantages outweigh the drawbacks, for which...

@tabatkins How would you accomplish what you want, as a feature in the language? I would say any implementation of support for that could be confusing to read. But you...

Yes exactly.

Not that I know of. Feel free to create one

The most obvious mistaken usage will be: ```javascript const x = new X(); //oops I forgot the await, I now have a Promise, not an X! ``` If the language...