On 1 May 2012 07:22, Alan Malloy a...@malloys.org wrote:
On Apr 30, 7:53 pm, kurtharriger kurtharri...@gmail.com wrote:
Sounds good. Ill submit a patch for walk. Im not real sure why apply
hash-map didnt work, but if figure it out Ill add that too.
For the same reason that (apply hash-map {1
Ill agree that it may be approriate for map? to return false as it does
perhaps imply a stricter contract then the jvm versions namely immutability.
However, I fully expected the return type of keywordize to be a new immutable
clojure map and it would be extreamly helpful if walk,
Sounds good. Ill submit a patch for walk. Im not real sure why apply hash-map
didnt work, but if figure it out Ill add that too.
--
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
On Apr 30, 7:53 pm, kurtharriger kurtharri...@gmail.com wrote:
Sounds good. Ill submit a patch for walk. Im not real sure why apply hash-map
didnt work, but if figure it out Ill add that too.
For the same reason that (apply hash-map {1 2, 3 4}) doesn't work: the
maps seqs as ([1 2] [3 4]), not
I am using a groovy library that returns a LinkedHashMap containing ArrayLists
and nested LinkedHashMaps. I did not expect any issues working with this in
clojure since this type implements java.util.Map I figured everything would
just work. However the first thing I tried to do was apply
Obviously, LinkedHashMap is not a Clojure persistent data structure.
map? and alikes tests interfaces specific to Clojure, not Java ones.
Clojure data structures implement java.util.Map and cie to ease interop
with Java but they are not the same as the persistent interfaces and do not
allow
Ill agree that it may be approriate for map? to return false as it does perhaps
imply a stricter contract then the jvm versions namely immutability. However,
I fully expected the return type of keywordize to be a new immutable clojure
map and it would be extreamly helpful if walk, hash-map,
