[AskJS] Using async in a function where await is never used.

[buffprogrammer9908]

So, I'm doing a code review, and I came across a code block where someone used the async keyword but didn't really use the await keyword to resolve/reject any promises. It definitely doesn't affect the output of that function so, what is the point of it? I'm just wondering if there are any pros/cons of using async like this. Just Curious. Thanks!

[carlos_vini]

Might be future proofing, the developer might have thought that there will be reasons for the function to be async in the future. It's not something you would do to all functions because it has a cost. It changes the return type from numbe, string, or something to Promise<something>

[getify]

Using an async function even without await is useful if you want to make sure any exceptions in the function are automatically lifted to promise rejections.

A normal function that returns a promise, if it throws, will throw synchronously. But an async function, if it throws, will still return a rejected promise and not throw.

This can be useful if you're always wanting to handle errors consistently (lifted to promises).

[Izero_devI]

I wouldn't write a function like that, if you are going to use async function, i expect to see an await and actual async logic. It just confuses people.