Amazing feedback everyone. Thank you.
--
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 unsubscrib
I am looking for a functional, non-blocking way to process the return of a
future. In the Scala world, you can use map, flatMap, and foreach to
process the return values of a future asynchronously. In Clojure,
dereferencing blocks, so that makes it kind of rough since we have to set
up our con
What is TDD culture in Clojure like? Is it strong in the community and
other projects? I am aware of Rich Hickey's guard rail analogy. Did that
have an effect on how Clojurists view TDD or testing in general? Just
asking for my own personal research.
--
You received this message because you a
me with
>> vanilla maps:
>>
>> (def employee [first-name last-name level]
>> {:first-name .})
>>
>> (defn promote [{:keys [level] :as employee]
>> (assoc employee :level (next-item levels level)))
>>
>> but that is just me - maybe I ran
This is for my language matrix project that has samples for 10 different
languages. My clojure knowledge is ok, but not really as great where I
would like it to be, therefore looking towards the community for help.
This example works, but it still has the feel of a lot of duplication, are
ther
