Ben it is not about the boilerplace and less typing or more typing, but I found myself having a hard time parsing those | for reading different types, because of that, having something like this, when you brain sees this automatically understands what is that type about, the parsing becomes easier.
Also from language perspective, I like to embrace this as type, like Haskell or Swift those with those Optional types (I dont need a optional type itself on elixir btw, just the typespec) but, that is just me, I can't speak for others. On Tuesday, February 27, 2018 at 4:11:39 AM UTC-8, Yordis Prieto wrote: > > Introducing `maybe(t)` it will reduce the boilerplate code for `nil | > something` > > It is more convenience to write it this way, at least for me. > > What are your thoughts about it? > -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/57e8c562-fff8-4ba0-8789-604a5a1aa550%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
