The problem is that this is more than just a syntactic difference. There's a chance it will take two ticks to resolve instead of one.
For documentation purposes, I recommend block-commenting the `async`:
const foo = /async/ () => new Promise(...);
I did not know this and appreciate the insight! Will definitely store this back of mind and try and remember to use block comments when needing to explicitly return a promise.
That's not true if you just return the promise instead of using return await, right?
I prefer
async function foo() { return await new Promise(...) }
as opposed to
function foo() { return new Promise(...) }
They're the same thing for the most part but the latter I have to potentially dig deeper into the function to confirm it returns a promise compared to the former.