コンビネータ:and_then
map()
was described as a chainable way to simplify match
statements. However, using map()
on a function that returns an Option<T>
results in the nested Option<Option<T>>
. Chaining multiple calls together can then become confusing. That's where another combinator called and_then()
, known in some languages as flatmap, comes in.
and_then()
は引数として与えられた関数にラップされた値を渡しますが、その値がNone
だった場合はNone
を返します。
In the following example, cookable_v3()
results in an Option<Food>
. Using map()
instead of and_then()
would have given an Option<Option<Food>>
, which is an invalid type for eat()
.
#![allow(dead_code)] #[derive(Debug)] enum Food { CordonBleu, Steak, Sushi } #[derive(Debug)] enum Day { Monday, Tuesday, Wednesday } // 我々は寿司の材料を持っていません。 fn have_ingredients(food: Food) -> Option<Food> { match food { Food::Sushi => None, _ => Some(food), } } // コルドン・ブルーのレシピも持っていません。 fn have_recipe(food: Food) -> Option<Food> { match food { Food::CordonBleu => None, _ => Some(food), } } // 料理を作るためには、材料とレシピの両方が必要。 // ロジックの流れを`match`のチェインで表します。 fn cookable_v1(food: Food) -> Option<Food> { match have_recipe(food) { None => None, Some(food) => have_ingredients(food), } } // `and_then()`を用いることで、同じことをよりコンパクトに表現できます。 fn cookable_v3(food: Food) -> Option<Food> { have_recipe(food).and_then(have_ingredients) } // Otherwise we'd need to `flatten()` an `Option<Option<Food>>` // to get an `Option<Food>`: fn cookable_v2(food: Food) -> Option<Food> { have_recipe(food).map(have_ingredients).flatten() } fn eat(food: Food, day: Day) { match cookable_v3(food) { Some(food) => println!("Yay! On {:?} we get to eat {:?}.", day, food), None => println!("Oh no. We don't get to eat on {:?}?", day), } } fn main() { let (cordon_bleu, steak, sushi) = (Food::CordonBleu, Food::Steak, Food::Sushi); eat(cordon_bleu, Day::Monday); eat(steak, Day::Tuesday); eat(sushi, Day::Wednesday); }