if you chain it with Option.map you get the best benefit! all your options can flow in pipes |> |> CREATE or receive OPTION --> MAP OPTION --> HANDLE NONE CASE (or else with or default), option are "containers" (also Result!), same as collections (list, seq, array), so they can be mapped, filtered, etc..
![[LIVE] : ONE ลุมพินี 85 | คู่เอก "ยอดเหล็กเพชร vs ผึ้งหลวง"](http://i.ytimg.com/vi/Qq_19bnnxEo/mqdefault.jpg)
Very nice. Less code is nearly always better code; when you know the helpers, your refactor is both more concise and clearer.
if you chain it with Option.map you get the best benefit! all your options can flow in pipes |> |>
CREATE or receive OPTION --> MAP OPTION --> HANDLE NONE CASE (or else with or default),
option are "containers" (also Result!), same as collections (list, seq, array), so they can be mapped, filtered, etc..