On Tue, Jul 3, 2012 at 1:01 AM, Robert Marianski <r...@marianski.com> wrote: > I can confirm that this patch resolves the issue for me. Thanks! > > As to whether null and undefined should be interchangeable, I'm not sure > what the right answer is. I think that depends on how many times > undefined is returned as a result from a cljs function. If it happens > pretty often, then we probably stand to benefit if they are > interchangeable. If it's infrequent, then we should probably just > normalize the results where this happens to always return nil instead of > undefined. I'm not familiar with the implementation, so I don't have a > good feel for the nuances here. > > By the way, can you currently extend a protocol to undefined? > > Thanks again, > Robert
JS undefined should always be treated as nil -- 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
