Re:Code optimizations when using async/await
by fathyb on Tuesday January 04, 2022 @11:52AM
(#29796875)
The error handler won't be called until the next tick:
Promise
.reject('error')
.catch(error => console.log('Error handler called:', error))
console.log('After reject')
This will print: After reject
Error handler called: error
Re:Code optimizations when using async/await
by lhorie on Tuesday January 04, 2022 @11:59AM
(#29796963)
I think the point is that try/catch in async code is tied to the presence of await. This will run happily without falling into the catch clause:
const err = async () => {
throw new Error('async error')
}
try {
const rejected = Promise.reject();
const errored = err();
console.log('ok!'); // in real code, this might have returned a deferred to be handled elsewhere instead
} catch (e) {
console.log('not ok!'); // never gets here
}
are you sure about that?
Promise.reject is synchronous and won't wait for the next tick it just returns a rejected promise
try/catch can be used fine