Hello.
Does anyone know why clojure.core/ns macro is not implemented as function?
It seems that it should work that way except that probably it would be
nicer to have in-ns call at the top level.
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To
Clojure 1.7 alphas are pretty solid. I use them in production without any
problems and with benefits of 1.7.
On Monday, December 29, 2014 5:38:05 PM UTC+1, Udayakumar Rayala wrote:
Hi,
We are currently using clojure 1.6.0 and using async channels version
0.1.346.0-17112a-alpha.
I see
Hi!
My first guess: a normal function evaluates all its arguments. ns uses
(:require ) (:use.. ) (:import ..) that should be not evaluated at ns
apply. The alternative is to make ns an special form, but macro should be
more flexible.
Instead, in-ns is simpler, and it can be implemented as a
That would be great, if possible! I did try looking yesterday with visualvm
to see what was going on, but some 50,000 findClass calls in, visualvm ran
out of memory and crashed. And then I got distracted ...
Jony
On Tuesday, 30 December 2014 07:22:02 UTC, Mikera wrote:
I'm trying to figure
On Dec 29, 2014, at 8:38 AM, Udayakumar Rayala uday.ray...@gmail.com wrote:
Is there any option other than upgrading to Clojure 1.7.0-alpha4? If not, how
safe it is right now to use Clojure 1.7.0-alpha4 in production? We really
want to use transducers as it makes our code readable.
We’ve
Hi,
FWIW I just put on a Clojurescript-specific subsite of CrossClj [1], that lists
and searches both cljs tools and projects (published on clojars/github) with at
least a .cljs source file (that includes projects developed with cljx)
http://crossclj.info/cljs
The auto-completing search field
I did the same recently, you can already leverage transducer support in
core.async while staying backward compatible with clojure 1.6. You loose
some sugar and the transducer versions of most sequences functions but it's
very usable still.
you can see 2 examples here:
I'm curious about the future Clojure 1.7 release. I recently looked over
these pages:
- Clojure JIRA Workflow
http://dev.clojure.org/display/community/JIRA+workflow
- Contributing to Clojure
http://dev.clojure.org/display/community/Contributing
- Next Release Planning
The Clojure JIRA Workflow page you linked to has several links on it to
'saved JIRA searches', which show only JIRA tickets matching specific
criteria. In the Dev patch section there are ones for all Needs a
patch tickets, for example, or all Incomplete tickets. For writing
patches, the Needs a
Hi David!
On Tuesday, December 30, 2014 4:01:27 PM UTC-6, David James wrote:
My questions are: (Please let me know if I've overlooked links to read.)
- Does Rich or Clojure Core have rough dates in mind for the 1.7
release? Any idea? (I wouldn't be surprised at all if dates were not
inc all the other responses in this thread but will also point at this
example in the core.async tests that defines a transducer (works in 1.6) as
an example:
https://github.com/clojure/core.async/blob/master/src/test/clojure/clojure/core/pipeline_test.clj#L6
On Monday, December 29, 2014
Andy and Alex: Thanks for the answers!
--
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
12 matches
Mail list logo
