Briefly, we may use those accounts for promoting Clojure, but who has the
accounts?
More:
https://www.reddit.com/r/Clojure/comments/7btc2k/who_owns_the_twitter_accounts_clojure/
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group,
I too ended up using a custom macro instead of `s/keys` everywhere. I
posted my solution somewhere above:
https://gist.github.com/metametadata/5f600e20e0e9b0ce6bce146c6db429e2
I didn't know it's possible to check if keys are registered at macro
expansion time, will try this out. Thanks Didier.
first and rest are defined in terms of position, and work on anything that
can be treated as an ordered collection
peek and pop work in terms of "natural insertion order" and only work with
things that behave like a stack - (so not lazy-seqs, strings, etc.)
lists push and pop from the front, vect
Using a dynamic language doesn't mean you should not think in terms of
(abstract) types; it only means that you're note relying on the compiler to
check types for you. If anything, that should encourage you to be more
disciplined in your thought processes (as you don't have anything else to
rely on
Hi fellow clojurians,
I just released the first alpha of task : https://github.com/leonoel/task
Task is a specification and toolkit to define and compose generic
computations in clojure.
I would appreciate any feedback on this project, be it about definitions,
design, or even on the relevance of
We've switched both of our main projects to RC1 and have had no issues yet.
On Thursday, November 9, 2017 at 11:49:07 PM UTC-8, Sean Corfield wrote:
>
> We have three processes running RC1 in production as of today. Looks good
> so far. We’ve had everything else up and running on Beta 4 in produc
One way to prevent that would be to only ever use aliases for fully
qualified keywords, never type out the whole thing.
On Thursday, November 9, 2017 at 11:22:24 PM UTC-8, Didier wrote:
>
> I just stumbled upon another potential mistake here. When you have specs
> split across namespaces. Its p
>
> One way to prevent that would be to only ever use aliases for fully
> qualified keywords, never type out the whole thing.
>
Uh, you forced me to go learn more about keywords. I didn't know you could
do ::namespace/name to alias keywords.
I've been manually namespacing my keywords until now
Is Clojure 1.9 expected to support JDK9? Or is that support reserved for a
later version?
On Friday, 10 November 2017 10:08:35 UTC-8, Beau Fabry wrote:
>
> We've switched both of our main projects to RC1 and have had no issues yet.
>
> On Thursday, November 9, 2017 at 11:49:07 PM UTC-8, Sean Corf
Clojure 1.9 (and 1.8, and every other prior version of Clojure!) works with
Java 9 due to the care that Java takes in retaining backward compatibility.
Clojure 1.0 works just fine with Java 9.
However, there have been some changes that affect various tools, most
prominently Leiningen and Boot.
10 matches
Mail list logo
