Why are her swollen fingers trying to eat the nails ? That ' s disgusting ! <| sep |> Farewell , ASOV 5 ! The map reset has me jazzed to play again <| sep |> Try Swifts optionals for a while , and you should relatively quickly get bothered by this very syntax . As others mention , there is no need for this feature . It would also be limited in usability , as functions that return multiple values would break the chain . In Swift , a language with this feature , you don ' t seem to ever make any chains . You may guard a method call with ? , causing its return value to also be optional , or assert the value as nonnil with ! , which would throw a runtime error on nil much like Go would panic . The former ends up being a nuissance , and a if nil , throw an appropriate error , otherwise , unpack with ! pattern emerges .