@Alex Miller: Please reconsider. What you state does not apply to 1.8, i. 
e. the ns is required in :or and such code is broken in 1.9

1.8/1.9 differences:
(let [{:keys [a/b] :or {b 42}} {}] 
  b)
=>
1.8: nil
1.9: 42(let [{:keys [a/b] :or {a/b 42}} {}] 
  b)
=>
1.8: 42
1.9: nil




On Wednesday, July 6, 2016 at 1:43:46 PM UTC+2, Alex Miller wrote:
>
> This is the correct behavior. The :or map keys are always the local names 
> being bound (not the keys being looked up in the map). 
>
> > On Jul 6, 2016, at 4:40 AM, Leon Grapenthin <grapent...@gmail.com 
> <javascript:>> wrote: 
> > 
> > Another small bug report: 
> > 
> > (let [{:keys [a/b] :or {a/b 42}} {}] 
> >   b) 
> > 
> > Evaluates to nil, but should evaluate to 42 
> > 
> > (let [{:keys [a/b] :or {b 42}} {}] 
> >    b) 
> > 
> > Evaluates to 42, but should evaluate to 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
--- 
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.

Reply via email to