Is it possible await to a function that is not a promise? Maybe a function that cannot fail.
for example:
async function doWork() { const newData = await cannotFail(); console.log("done: "+ newData); } function cannotFail() { var data = //cannot fail code . . . return data; } doWork(); I was thinking maybe with another syntax this option makes sense.
Consider these two examples
async function getData(){ return "some data"; } async function doSomething() { const data = await getData(); console.log(data); } doSomething()function getData(){ return "some data"; } async function doSomething(){ const data = getData(); console.log(data); } doSomething();The result is exactly the same. You only use await when you want to wait for an asnyc function like it is synchronous. Normal functions already are synchronous.
And yes it is possible to use await on a normal function
function getData(){ return 'some data'; } async function doSomething(){ const data = await getData(); console.log(data); } doSomething();There is just no reason to.
await onConfirm();closeModal()It is possible to use await with an expression that does not evaluate to a promise. Whether that is useful, is questionable.
First of all, when await is followed by an expression that does not evaluate to a promise object, it is turned into one -- a resolved promise.
The main difference you get by using await with a non-promise or a resolved promise, is that await will make the async function return. This behaviour is not dependent on whether the promise is already resolved or not. await always postpones the further execution of the function by placing that resuming-job on the promise job queue.
See the difference here:
async function test() { let a = 1; // Without await console.log(a); return 2; } test().then(console.log); console.log("end of main, synchronous code");And with await
async function test() { let a = await 1; // With await console.log(a); return 2; } test().then(console.log); console.log("end of main, synchronous code");Note the different order of execution.
console.log need to wait to the a variable in order to log it even if you dont add the await.
async, it will wait for it either way?". If you refer to the expression that follows await, the rule is: if that expression is a promise (which is the case when you call an async function there), then await will await that promise to be resolved. It the expression does not evaluate to a promise (which is the case when you call a non-async function there), then await will treat that expression as a resolved promise. It will still make the function return first.await always makes the wrapping async function return. The remaining code that follows below an await is never executed immediately. Never. That remaining code is always called from the event queue.console.log need to wait to the a variable": that is an odd way to phrase it. The code that follows below an await (like that console.log) is never executed immediately. The function's execution context is saved when an await executes. It has nothing to do with the expression that the await operates on. It can be anything. It can be null, it can be 1, it can be the evaluation of a function. Whatever it is, await will make the wrapping function to return. Always.It's not necessary, but it is possible:
const newData = await Promise.resolve( cannotFail() ); 
cannotFailfunction contains an async code that is callback-based, you can wrap a promise around it and return that promise from thecannotFailfunction.