從一個(gè)討論開始,Node 8 LTS 有 async 了很興奮? 來,說說這 2 段代碼的區(qū)別。
async function rejectionWithReturnAwait () {
try {
return await Promise.reject(new Error());
} catch (e) {
return 'Saved!';
}
}
async function rejectionWithReturn () {
try {
return Promise.reject(new Error());
} catch (e) {
return 'Saved!';
}
}
上面的代碼幾乎相同,只是第一段中在Promise函數(shù)前有一個(gè)await關(guān)鍵字,但是兩段代碼的運(yùn)行效果確實(shí)千差萬別。想要了解其中緣由,且聽我娓娓道來。
1. Nodejs想說愛你不容易
Node.js? is a JavaScript runtime built on Chrome's V8 JavaScript engine. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient. Node.js' package ecosystem, npm, is the largest ecosystem of open source libraries in the world.
基于Javascript的語法、非阻塞單線程的特性,使得nodejs在處理I/O時(shí)非常麻煩。破解之道依次經(jīng)歷過callback瀑布級回調(diào)嵌套、Promises函數(shù)、Generator函數(shù) 詳細(xì)參見我的另外一篇學(xué)習(xí)筆記Nodejs 異步處理的演進(jìn)。
盡管社區(qū)和ECMA管委會(huì)不斷提出解決異步的方案,但是仍不能滿足神經(jīng)質(zhì)的開發(fā)人員對清潔代碼矢志不渝追求。直至在ES7中async函數(shù)的出現(xiàn),很快Nodejs社區(qū)也在7.6版本中添加了async函數(shù),至此Nodejs無縫鏈接async函數(shù),Nodejs異步的難題才算是取得了里程碑式的進(jìn)展。
2. 偷窺Async函數(shù)
先從一段代碼開始:
// await 關(guān)鍵字后的函數(shù)
var Delay_Time = function(ms) {
return new Promise(function(resolve) {
setTimeout(resolve, 1000)
} )
}
// async 函數(shù)
var Delay_Print = async function(ms) {
await Delay_Time(ms)
return new Promise(function(resolve, reject) {
resolve("End");
})
}
// 執(zhí)行async函數(shù)后
Delay_Print(1000).then(function(resolve) {
console.log(resolve);
})
上面的示例代碼定義了三個(gè)方法塊,分別是async 聲明的函數(shù)體、await 執(zhí)行的函數(shù)體、async 函數(shù)執(zhí)行后的函數(shù)體。整段代碼執(zhí)行的結(jié)果是在1000毫秒后,控制臺(tái)打印出“End”。
通過整段代碼我們可以看出:
a. 在函數(shù)體前通過關(guān)鍵字async可以將函數(shù)變?yōu)閍sync函數(shù)
b. 在async函數(shù)中對需要異步執(zhí)行的函數(shù)前需加await關(guān)鍵字
c. await后的函數(shù)必須使用Promise對象封裝
d. async函數(shù)執(zhí)行后返回的是一個(gè)Promise對象
3. async與await這對大寶貝
Promise對象狀態(tài)的變化
var delay_print_first = function() {
return "First";
}
var delay_print_second = function() {
return Promise.resolve("Second");
}
var delay_print_third = function() {
return Promise.resolve("Third");
}
var async_status = async function(ms) {
var first = await delay_print_first();
var send = await delay_print_second();
var third = await delay_print_third();
return first + " " + send + " " + third;
}
async_status().then((ret)=> {
console.log(ret); // First Second Third
});
async函數(shù)必須要等到方法體中所有的await聲明Promise函數(shù)執(zhí)行完后,async函數(shù)才會(huì)得到一個(gè)resolve狀態(tài)的Promise對象。
如果在執(zhí)行async中的異步函數(shù)的過程中,一旦有一個(gè)異步函數(shù)出現(xiàn)錯(cuò)誤,整個(gè)async函數(shù)就會(huì)立即拋出錯(cuò)誤,但是如果在async函數(shù)中對異步函數(shù)通過try/ catch封裝,并在catch方法體中返回Promise.reject(),這樣async函數(shù)將得到一個(gè)reject狀態(tài)的Promise,有效的避免因?yàn)楫惒胶瘮?shù)導(dǎo)致整個(gè)async函數(shù)的終止。
為了有效的記錄下error的信息,通常會(huì)在async執(zhí)行后做一些Promise catch的處理。 如下面的代碼:
var delay_print_first = function() {
return "First";
}
var delay_print_second = function() {
return Promise.resolve("Second");
}
var delay_print_third = function() {
return Promise.reject("Third");
}
var async_status = async function(ms) {
try {
var first = await delay_print_first();
var send = await delay_print_second();
var third = await delay_print_third();
return first + " " + send + " " + third;
} catch (error) {
return Promise.reject("Some error")
}
}
async_status().then((ret)=> {
console.log(ret);
}).catch((err) => {
console.log(err); // Some error
});
await關(guān)鍵字的作用
async中的函數(shù)如果不使用await聲明就是普通函數(shù)
var Delay_Time = function(ms) {
return new Promise(function(resolve) {
setTimeout(resolve, ms)
} )
}
var Delay_Time_Second = function (ms) {
setTimeout(function() {
}, ms);
}
var Delay_Print = async function(ms) {
Delay_Time_Second(2000);
console.log("After Delay_Time_Second")
await Delay_Time(ms)
console.log("After Delay_Time")
return new Promise(function(resolve, reject) {
resolve("END");
})
}
Delay_Print(2000).then(function(resolve) {
console.log(resolve);
})
上面的代碼的執(zhí)行結(jié)果是:
a. 立即打印出"After Delay_Time_Second"
b. 過了2000毫秒后打印出 "After Delay_Time"
c. 最后打印出"END"
在正常的情況下,await后是一個(gè)Promise對象。如果不是就會(huì)立馬轉(zhuǎn)換成一個(gè)立即resolve的Promise對象。
var await_fun = async function() {
return await "END";
}
await_fun().then((ret) => {
console.log(ret); //END
})
上面代碼中async的方法體,相當(dāng)于下面
var await_fun = async function() {
return Promise.resolve('END');
}
多個(gè)函數(shù)并發(fā)執(zhí)行
如果async中的多個(gè)函數(shù)是在執(zhí)行的先后沒有要求,最好把多個(gè)函數(shù)變?yōu)椴l(fā)執(zhí)行。
async function dbFuc(db) {
let docs = [{}, {}, {}];
let promises = docs.map((doc) => db.post(doc));
let results = await Promise.all(promises);
console.log(results);
}
如果async函數(shù)體中有多個(gè)await 聲明的函數(shù),且await 之間是并發(fā)的,await聲明的函數(shù)體是繼發(fā)的,見如下代碼:
var delay_time = function(ms, param) {
return new Promise(function(resolve) {
setTimeout(function() {
console.log(new Date().getTime());
resolve(param);
}, ms)
} )
}
var asyn_fun = async function (params) {
var time_out = 1000;
const results = await params.map(async param => {
time_out = time_out + 1000;
var out = await delay_time(time_out, param);
return out
});
var target = [];
for(var ret of results) {
target.push(await ret);
}
return await target;
};
asyn_fun(['First','Second','Third','Last']).then(function(result){
console.log(JSON.stringify(result)) // ["First","Second","Third","Last"]
});
雖然map方法的參數(shù)是async函數(shù),但它是并發(fā)執(zhí)行的,因?yàn)橹挥衋sync函數(shù)內(nèi)部是繼發(fā)執(zhí)行,外部不受影響。后面的for..of循環(huán)內(nèi)部使用了await,因此實(shí)現(xiàn)了按順序輸出。
4. 最后回到開篇的問題
async function rejectionWithReturnAwait () {
try {
return await Promise.reject(new Error());
} catch (e) {
return 'Saved!';
}
}
rejectionWithReturnAwait().then((ret) => {
console.log(ret); // "Saved"
})
這段代碼在async方法體中通過try/catch捕獲被await聲明并且狀態(tài)是rejected的Promise對象,捕獲異常后返回立即執(zhí)行的Promise對象。
async function rejectionWithReturn () {
try {
return Promise.reject(new Error());
} catch (e) {
return 'Saved!';
}
}
rejectionWithReturn().then((ret) = > {
console.log(ret);
})
上面async代碼快內(nèi)的Promise對象沒有使用await關(guān)鍵字聲明,因?yàn)楫?dāng)Promise對象的狀態(tài)由pending變成rejected后并不能try/catch捕獲,代碼的執(zhí)行結(jié)果如下:
(node:50237) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 5): Error
(node:50237) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.