I agree with the stance that nil is a value and it is the responsibility of the caller to throw if nil indicates an error in the calling context.
On Wednesday, January 13, 2016 at 4:25:56 AM UTC+8, mattias w wrote: > > Clojure and Erlang are very similar, except for the syntax, macros and > that you can use Java libraries. > > There is one big difference: In Erlang, fail as early as possible is the > norm. In Clojure it is almost the opposite. > > Many errors in Clojure code will result in nil, and most operations accept > nil as a valid parameter, i.e. many fails will not even be visible unless > you check the result. > > The most common I stumble on is assuming that a value exists in a map, but > that is just the top of the iceberg > > I assume Rick H did this on purpose, and I am looking for pointers to > where the rationale behind is described. > > Thanks, > > Mattias > > > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
