That is what I figured/suspected but wasn't sure. Thanks for filing those
pull requests so quickly!
Alan
On Fri, Aug 19, 2016 at 10:32 PM, Alex Miller wrote:
> system also depends on the latest released version of monger, which has an
> invalid defn in it (:or [ ] instead of :or { }) in monger
system also depends on the latest released version of monger, which has an
invalid defn in it (:or [ ] instead of :or { }) in monger.core. afaict,
this problem has been fixed in master of monger, but no new version is
available yet.
On Saturday, August 20, 2016 at 12:15:08 AM UTC-5, Alex Mille
Those are bugs in system. When you see "(system.repl (require
[com.stuartsierra.component :as component] ..." those are the arguments to
the ns form, so the "system.repl" is the namespace name. You cut out the
stack trace, but I'd expect the top frame to be in that ns.
PRs filed at https://gith
All,
Is anyone else experiencing problems using danielz/system and/or
stuartsierra/component? I'm getting the following:
Caused by: java.lang.IllegalArgumentException: Call to clojure.core/ns did
not conform to spec:
In: [1] val: ((require [com.stuartsierra.component :as component]
[clojure.to
The cljsbuild.crossover namespace has (import …) instead of (:import …) – file
a bug report against that project so the maintainer can update it to be
compatible with Clojure 1.9.0.
The error message says In: [3 0] so you can see it is the 0th element of the
item with index 3 in the ns form tha
Great - thanks Alex! All the efforts around clojure.spec will definitely
bring consistency in the world of Clojure codebases : )
On Friday, August 19, 2016 at 9:05:16 PM UTC-7, Alex Miller wrote:
>
> That looks like a bug in lein-cljsbuild. cljsbuild/crossover.clj is
> failing due to (import jav
That looks like a bug in lein-cljsbuild. cljsbuild/crossover.clj is failing
due to (import java.io.File java.net.URLDecoder) - should be (:import
java.io.File java.net.URLDecoder).
PR filed here: https://github.com/emezeske/lein-cljsbuild/pull/447
On Friday, August 19, 2016 at 9:55:17 PM UTC-
Ran into this problem with ClojureScript/ReactNative/Re-natal project:
Compiling ClojureScript...
Exception in thread "main" java.lang.IllegalArgumentException: Call to
clojure.core/ns did not conform to spec:
In: [3 0] val: import fails spec: :clojure.core.specs/ns-refer-clojure at:
[:args :c
I saw your PR for io.aviso/pretty ... thanks!
I can't imagine how much work it must be to track all of those things down
...
On Friday, 19 August 2016 11:35:31 UTC-7, Alex Miller wrote:
>
> One thing to note is that the new specs for clojure.core means that there
> is a reasonable amount of (br
I'm not convinced this is even a good idea (but Rich is the ultimate
judge). None of the -in fns repeat paths like that so this makes assoc and
assoc-in similar but makes assoc-in / update-in etc inconsistent.
On Friday, August 19, 2016 at 1:50:41 PM UTC-5, Łukasz Kożuchowski wrote:
>
> On 08/
On 08/18/2016 09:46 PM, Andy Fingerhut wrote:
Anyone who has created a free JIRA account can vote on Clojure tickets.
Wow. That's nice. Just voted. Thanks for the info. I thought it's only
for contributors.
I'm not really complaining, just wanted to know what's going on and
possibly bump th
I have released a library for fusing a stream, decoder, and resource
management into a reducible object with the intent to automatically manage
resources. You can then apply a transducer to this object. This means you
can apply a transducer pipeline that only partially consumes the stream,
yet
One thing to note is that the new specs for clojure.core means that there
is a reasonable amount of (broken) code in the wild that now does not
compile.
I have filed PRs in a number of commonly used projects and while those were
all merged, most have not yet been released into new versions yet.
Clojure 1.9.0-alpha11 is now available.
Try it via
- Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.9.0-alpha11
- Leiningen: [org.clojure/clojure "1.9.0-alpha11"]
1.9.0-alpha11 includes the following changes since 1.9.0-alpha10:
Clojure now has specs for the following clojure.co
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
Leiningen dependency information:
[org.clojure/clojurescript "1.9.225"]
A bug fix release for cljs.spec and a REPL regression.
As always feedback welcome!
##
"We're in an exciting phase right now as we're transitioning to
programmatic buying and selling of Advertisement space. The amount of
non-trivial challenges in our horizon is huge and the learning
opportunities are never-ending. From intelligently bidding for
Advertisement space in real time, t
What I meant was that you can spec the defmulti, and code runs just fine,
but you can't instrument it. As then you end up with the instrumentation
wrapper not being a multimethod, so things break. That's how I read the
stack trace. It'd seem possible for instrument to wrap the multimethod with
17 matches
Mail list logo
