Yeah, laziness on my part, I was just trying to show that everything
after '&' comes in as a list, and you can be creative if you need to
be. I use this on occasion for macros with multiple different types
of optional arguments.
On Sun, Nov 27, 2011 at 6:45 PM, Alan Malloy <a...@malloys.org> wrote:
> On Nov 27, 8:43 am, Mark Rathwell <mark.rathw...@gmail.com> wrote:
>> Also, another way to take keyword arguments is:
>>
>> (defn foo [& opts]
>> (let [opts (apply hash-map opts)]
>> (println opts)))
>
> This is what already happens internally with the & {:keys ...}
> notation. You can actually be rather more concise if you write:
>
> (defn foo [& {:as opts}]
> (println opts))
>
> --
> 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 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
