On Jun 2, 2015, at 2:13 PM, Elric Erkose <elric.erk...@gmail.com> wrote: > Is it reasonable that ```(slurp nil)``` throws an Exception rather than > evaluates to nil?
IMO, yes, throwing an exception is the right thing here, otherwise you’d have nil instead of a string and you’d likely be doing string operations on it, many of which fail when given nil. I would expect passing nil to slurp to be an exceptional situation that you’d either want to explicitly check for beyond hand or handle via try/catch after the fact. Sean Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- 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.
