I am trying to call into some Scala that has the following overloaded
methods :
def apply[T](clauses: (Double, Element[T])*)(implicit name: Name[T],
collection: ElementCollection) =
new AtomicDist(name, clauses.toList, collection)
def apply[T](clauses: (Element[Double],
I always have (:use clojure.core) in a new namespace. Is that necessary or is
clojure.core is automatically interned when a new namespace is created?
On Jun 23, 2015, at 6:37 AM, Gary Verhaegen gary.verhae...@gmail.com wrote:
Unless you have a very compelling reason, just don't use use. It's
Hi Gregg,
When you look at the function given as the first argument to 'recurse', (fn
[f g] #(f (apply g %))), how do you think about when '%' is replaced
by [1 2 3 4]? Does this happen only when 'recurse' has consumed all the
items in the collection it's been given (as the second
Hello everyone.
I'm happy to announce the initial release of Yagni, a Leiningen plugin for
finding unused code.
At a high level, Yagni works by identifying all of the interned vars in the
namespaces findable within your :source-paths, and then walking the forms
of those vars.
As it walks
I see. Thanks.
On Jun 23, 2015, at 11:02 AM, Fluid Dynamics a2093...@trbvm.com wrote:
On Tuesday, June 23, 2015 at 10:40:25 AM UTC-4, Ritchie Cai wrote:
I always have (:use clojure.core) in a new namespace. Is that necessary or is
clojure.core is automatically interned when a new namespace
When exactly does this appear? It's just a file used by Clojure for code
evaluated in a REPL, but shouldn't appear in CIDER at all (except in
stacktraces).
On 23 June 2015 at 18:56, dtouch3d completely dtouc...@gmail.com wrote:
Is there a way to disable the /tmp/form-init*.clj buffer from
Is there a way to disable the /tmp/form-init*.clj buffer from showing when
there is an error in evaluation ? It can be very annoying as I am new to
clojure and emacs and it replaces my source file buffer and provides no
useful information. The cider-error buffer is more than adequate for
On Tuesday, June 23, 2015 at 10:40:25 AM UTC-4, Ritchie Cai wrote:
I always have (:use clojure.core) in a new namespace. Is that necessary or
is clojure.core is automatically interned when a new namespace is created?
It depends. Yes if you use (ns foo) ..., but not apparently if you use
It appears when I try to evaluate code that has syntactic errors.
On Tuesday, June 23, 2015 at 7:42:10 PM UTC+3, Bozhidar Batsov wrote:
When exactly does this appear? It's just a file used by Clojure for code
evaluated in a REPL, but shouldn't appear in CIDER at all (except in
stacktraces).
Submit a ticket to the issue tracker with some repro steps and I'll take a
look at it. I've never seen this behaviour (and nobody has reported it so
far), so I'm guessing something in your setup is uncommon.
On 23 June 2015 at 21:27, dtouch3d completely dtouc...@gmail.com wrote:
It appears when
Hi Atamert - thanks :)
I thought it might be preferable to keep the call to (latch)explicit - it
means that ylet can be used in nested calls, too - for example, to set up
and compose groups of components/sub-systems: (contrived example, though!)
;; (docs for ylet at
Matching Socks, thanks for mentioning the design page I created.
I haven't pushed anything recently, but I'm still working on the rewrite
implementing the proposal: https://github.com/bendlas/data.xml
I've also made a library, that uses a snapshot from my rewrite to implement
a WebDAV server:
On Tue, Jun 23, 2015 at 11:19 AM, Mike Grabowski grab...@gmail.com wrote:
Hey guys,
I am so excited to join Clojure bandwagon, last weeks have been super
exciting, pretty much in love with Clojure syntax. As we are currently
building an application broken into smaller micro services, I
Hey guys,
I am so excited to join Clojure bandwagon, last weeks have been super
exciting, pretty much in love with Clojure syntax. As we are currently
building an application broken into smaller micro services, I thought I am
gonna make one or two Clojure based modules. Although the initial
Hi James,
Interesting idea. Thanks for sharing.
I think you can simplify this:
(yoyo/run-system!
(fn [latch]
(ylet [db-pool (with-db-pool {...})
:let [server-opts {:handler (make-handler {:db-pool db-pool})
:port 3000}]
web-server
Unless you have a very compelling reason, just don't use use. It's mostly a
historical accident that's kept there for backwards compatibility.
And try to avoid :refer :all if possible. There are legitimate use-cases
for it, but outside the REPL they are pretty rare.
On Tuesday, 23 June 2015,
There is also a git annex command. I have not use it personally, but my
understanding is that it is essentially keeping a hash of the file (and
perhaps a url to download it?) in source control in git, without adding the
file itself.
That way git can tell when the file has changed, without
Oh fantastic! I was 100% wrong in literally the best way.
Thanks!
On Tue, Jun 23, 2015 at 7:17 PM, Ghadi Shayban gshay...@gmail.com wrote:
Good question.
Clojure's evaluation semantics dictate that the arguments are evaluated
(computed) *before* calling the function. So(set coll) is
Let's say that, as part of an xf, I want to filter out everything in a
sequence that's also in some other sequence. Here are some ways of doing
that:
(defn filter-contains1 [edn-file] (remove (partial contains? (set
(read-edn-file
edn-file)
(defn filter-contains2 [coll] (remove (partial
Good question.
Clojure's evaluation semantics dictate that the arguments are evaluated
(computed) *before* calling the function. So(set coll) is computed before
being passed to `partial`. Partial receives a function (a value) and
arguments (also values) and returns back a new function that
On Tue, Jun 23, 2015 at 4:17 PM, Ghadi Shayban gshay...@gmail.com wrote:
Tangentially:
(remove even?)
Will be faster than
(remove (fn [i] (even? i)))
because in the first case the dereference of the var 'even?' happens only
once and the value inside the var will be passed to `remove` at
21 matches
Mail list logo
