This fails:
(ns-resolve 'sumtin 'clecs.world/remove-entity)
Exception No namespace: sumtin found clojure.core/the-ns (core.clj:3830)
But this succeeds:
(ns-resolve 'seesaw.core 'clecs.world/remove-entity)
#'clecs.world/remove-entity
It seems when the 2nd argument is fully qualified, first a
It's talking about fully qualified symbols that map to an actual var.
E.g
user=> (ns-resolve *ns* 'clojure.string/join)
#'clojure.string/join
Brian Marick writes:
> The last sentence of the `ns-resolve` documentation reads:
>
>Note that
>if the symbol is fully qualified, the var/Class t
Could you clarify why you expect that?
Thanks,
Ambrose
On Thu, Apr 23, 2015 at 6:43 PM, Brian Marick wrote:
> The last sentence of the `ns-resolve` documentation reads:
>
> Note that
> if the symbol is fully qualified, the var/Class to which it resolves
> need not be present in the namesp
The last sentence of the `ns-resolve` documentation reads:
Note that
if the symbol is fully qualified, the var/Class to which it resolves
need not be present in the namespace.
What does that mean? I would expect something like the following to
produce a non-nil value:
user=> (ns-res
On Thu, Apr 23, 2015 at 1:34 AM Paul deGrandis
wrote:
>
> I'd also encourage you to reconsider your benchmark - ask yourself, "What
> does this really tell me?" Is the benchmark an accurate representation of
> the kinds of HTTP services you build? Are the payloads (parsing and
> generation) rep
Has anyone written a guide, or best-practices doc for converting clojure
libs to clojurescript?
I'm thinking of things like "what to do with java methods calls?" Write
shim objects? Convert all the method calls to protocols?
I expect this has been done many times, especially for common needs, l
Located in munich, germany.
I have used the language since 2010, experience with the clojure webstack,
shipped code to production for a big german fashion website.
Looking for remote work, does not matter if it is a small project or you
looking for long-term employees.
--
You received this m
I've opened an enhancement ticket with a patch that changes this
behaviour btw: http://dev.clojure.org/jira/browse/CLJ-1715
Alexey Cherkaev writes:
> Hi,
>
> I have encountered the problem with Clojure 1.6.0, when I create the record
> that implements IFn.
>
> For example,
>
> (defrecord Foo [x]
You're not implementing IFn.applyTo, you should.
Why applyTo is used in the second example while invoke is used in the
other cases has to do with implementation details of how def expressions
are compiled/evaluated.
Alexey Cherkaev writes:
> Hi,
>
> I have encountered the problem with Clojure 1
Hi,
I have encountered the problem with Clojure 1.6.0, when I create the record
that implements IFn.
For example,
(defrecord Foo [x]
clojure.lang.IFn
(invoke [_ f] (f x)))
Than create an instance of this record:
(def f (->Foo 10))
And we can call it without a problem:
user=> (f inc)
10 matches
Mail list logo
