On Fri, Oct 21, 2011 at 11:22 AM, David Nolen <dnolen.li...@gmail.com> wrote: > Collections often include false as a value. You will have to handle it by > using some other value like ::not-found. > > David
True, but the multiple meanings of nil creates additional complexity. Contrast, for example, (filter identity s) and (keep identity s). One strips nil and false values, the other just strips nil values. Why do we need both? Because sometimes we mean nil and false to be the same, and sometimes we don't. Have you ever gotten this wrong? I have, and I understand these issues pretty well. Maybe you haven't, maybe you can "juggle more balls" than I can. But as Rich pointed out in the video, simplicity is about respecting the fact that all of our brains have limitations and can get tripped up when things are complected. -- 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
