Should awaiting a non-Promise value be an error?

[Arnavion]

TypeScript Version:

1.9.0-dev.20160426

Code

var x = await 5;

Currently this compiles just fine and behaves correctly at runtime. But is there a situation where the user would want to deliberately await a non-Promise? Or should it be a compiler error?

---

I thought of:

1. Normalizing a sync-or-async value:

   declare function mayReturnSyncOrAsyncResult(): number | Promise<number>;
   
   var result = await mayReturnSyncOrAsyncResult(); // number

   Either await could still be allowed for unions that contain Promise, or the user could be required to use await Promise.resolve instead of just await.

2. Extracting the value of a thenable:

   declare function foo(): bluebird.Promise<number>;
   
   var result = await foo(); // number

   Again await could still be allowed, or the user could be required to use await Promise.resolve

3. Deliberately introducing a yield point to make the rest of the function be a separate async continuation. I'm not sure if such a use actually exists in the wild. If it does exist, it too can be handled by await Promise.resolve

The downside of await Promise.resolve is that it introduces one extra Promise, since await will wrap the awaited value in one anyway.

I'm not completely convinced one way or the other. Opening this issue to get TS team's and other people's thoughts.

---

Alternatively I suppose we can make a tslint rule for "stricter awaits" or something.

[basarat]

But is there a situation where the user would want to deliberately await a non-Promise? Or should it be a compiler error?

Yes. When the API consumer wants a promise but the API provider doesn't need to be async. The provider code can then just await 🌹

[basarat]

instead of

function foo(){
      return Promise.resolve(3);
}

you get to

async function foo(){
      return await 3;
}

[Arnavion]

@basarat That should be

async function foo() {
    return 3;
}

[basarat]

That should be return 3

Indeed. Sorry. I know I should have been sleeping at that time 🌹

[mhegazy]

// CC @bterlson

I believe it is not an error to await a non-thenbale non-promise object. awaiting a literal as in the example should be equivalent to await Promise.resolve(3). @bterlson can point to the spec details.

one thing to note, var x = await 5; is not the same as var x = 5;; var x = await 5; will assign x 5 in the next tern, where as var x = 5; will evaluate immediately.

[Arnavion]

Yes, I said all that in the OP.

[basarat]

But is there a situation where the user would want to deliberately await a non-Promise

This is the heart of the question by @Arnavion ^.

Me : I can't think of a good reason. The only use case (next tern) is not one the user should be depending upon. There might be some obscure debounce style stuff that one can cook up 🌹

[mhegazy]

@bterlson, can you shed some light on the rational/motivating use cases for the current design?

[tp]

Just some anecdotal info: I got unwanted behavior when writing my first TypeScript program, since in many libs the TS version uses *Async names for the Promise-returning version of the function.

So since the callback was optional, I "awaited" on void and then the program would continue too early...

So if there no real reason to keep this behavior, I can assure you that this has already created some bug (even though luckily only during development).

[bterlson]

The goal of the current semantics isn't to allow uselessly awaiting known synchronous values but instead to allow awaiting maybe-promises and to align with the semantics of various existing promise utilities including Promise.resolve (promises and thenables unwrapped, values passed through) and then handlers (returned promises and thenables unwrapped, values passed through).

[mhegazy]

Thinking about this more, this could be enforced under a flag, by default if the compiler can attest that the type of await expression can not be a promise, then it should report an error, if the flag is set, the error reporting is skipped.