clojure.spec and the rest of clojure

Rich's session on the Cognicast brought up interesting questions for me. - Is Clojure.spec being applied within clojure.core and other parts of the language? - Has the test.check capability led to the discovery of bugs in clojure.core and other parts of the language? - Does anyone (else) antici

Re: [ANN] Clojure 1.9.0-alpha5

On 13 June 2016 at 03:29, Alan Thompson wrote: > I would have expected the namespaces to avoid this kind of conflict. Why > don't they? > All the vars in the clojure.core namespace are automatically imported into a namespace when it's created. It's why you can write (+ 1 1) instead of (clojure.c

Re: why is it so annoying to run clojure code

Check out natal, renatal or any of the other react native libraries/tools found here: http://cljsrn.org/ Alan -- 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 mem

Re: [ANN] Clojure 1.9.0-alpha5

On Sunday, June 12, 2016 at 10:29:56 PM UTC-4, Alan Thompson wrote: > > I would have expected the namespaces to avoid this kind of conflict. Why > don't they? > Because the conflict was only introduced five days ago, with this commit

Re: instrumenting clojure.core

> On Jun 12, 2016, at 10:45 AM, Alex Miller wrote: > > Still much to be determined about this but I expect that specs for core will > be provided and maintained by us, because while there are a lot of obvious > specs in core, there are also a lot of far more subtle ones. I think this is the ri

Re: [ANN] Clojure 1.9.0-alpha5

I would have expected the namespaces to avoid this kind of conflict. Why don't they? Alan On Sun, Jun 12, 2016 at 6:29 PM, James Reeves wrote: > On 13 June 2016 at 01:21, Alan Thompson wrote: > >> I am also getting a conflict with Plumatic Schema: >> >> WARNING: Inst already refers to: #'clojur

Re: instrumenting clojure.core

Hi Leon, I think you're looking for fspec , unless I'm misunderstanding something. I wrote up an example that might be helpful. @Ryan t

Re: why is it so annoying to run clojure code

On 12 June 2016 at 02:40, Antonin Hildebrand wrote: > > I assume those concepts are basic to someone with experience with java. > I'm sorry for my ignorance. My path was ... -> Javascript -> ClojureScript > -> Clojure. Not Java -> Clojure -> ClojureScript. > I don't think you need to be sorry for

Re: [ANN] Clojure 1.9.0-alpha5

On 13 June 2016 at 01:21, Alan Thompson wrote: > I am also getting a conflict with Plumatic Schema: > > WARNING: Inst already refers to: #'clojure.core/Inst in namespace: > schema.core, being replaced by: #'schema.core/Inst > > > I can't seem to find a reason for this warning, as I don't use Inst

Re: Clojars will be partially down for maintenance this weekend

Clojars is back up; we ran in to an issue with the update, so had to roll it back. Once we fix the issue, we'll schedule another maintenance window. Please file an issue[1] if you experience any problems. - Toby [1]: https://github.com/clojars/clojars-web/issues On Fri, Jun 10, 2016 at 4:01 PM,

Re: [ANN] Clojure 1.9.0-alpha5

I am also getting a conflict with Plumatic Schema: WARNING: Inst already refers to: #'clojure.core/Inst in namespace: schema.core, being replaced by: #'schema.core/Inst I can't seem to find a reason for this warning, as I don't use Inst anywhere and always say (require [schema.core :as s] ...)

Re: [ANN] Clojure 1.9.0-alpha5

On Thursday, June 9, 2016 at 11:40:03 PM UTC-7, Rangel Spasov wrote: > > Add the latest tools.analyzer as a dependency solved the problem. > > [org.clojure/tools.analyzer "0.6.9"] > >> >> I had the same problem and had to add this dependency. Is this expected? Using lein-collisions found no c

Re: instrumenting clojure.core

Alex, thank you for the long and detailed response. The direct linking issue and Ryans last example make me wonder whether the hard rule "If A and B are both instrumented and if A ever calls B violating B's spec, A's spec is broken" holds? If so the direct-linking issue would probably be a n

Re: What I'm missing in my Instaparse rules?

Regular expressions are treated with their ordinary Java/Clojure, greedy semantics. Your regular expression for ITEM doesn't exclude whitespace or } characters, so ITEM is matching "Harden }" which leaves no characters left to match your grammar's right curly brace requirement. => (re-seq #"[^\"]

What I'm missing in my Instaparse rules?

Hello, I'm playing around Instaparse library, starting very simple. For input like : { player } I created the following parser: (def ast (ist/parser "TEST = OBJECT = <#'\\s+'> = <'{'> = <'}'> ITEM = #'[^\"]+' OBJECT = CURLY_OPEN WHITESPACE* ITEM WHITESPACE* CURLY_C

Re: [GSoC Idea] Distributed Load Testing Tool in Clojure

Hello, I was reading the mailing list and http://dev.clojure.org/display/community/Project+Ideas+2016 looking for open source project ideas and found this. However, someone has likely implemented what you are looking for: https://github.com/mhjort/clj-gatling More ideas are appreciated. sexta

Re: instrumenting clojure.core

On Sunday, June 12, 2016 at 9:22:24 AM UTC-5, Leon Grapenthin wrote: > > That looks great already. I'm also interested in what the official > workflow for adding specs to core is going to be and whether contributions > are desired. > Still much to be determined about this but I expect that spec

Re: Bug (in Clojure 1.5): (fn [& xs] (pop xs)) throws ClassCastException clojure.lang.ArraySeq cannot be cast to clojure.lang.IPersistentStack

On Sunday, June 12, 2016 at 9:12:08 AM UTC-5, Fluid Dynamics wrote: > > That misses the point that we have a core function that throws a > ClassCastException when passed (seq x) and not when passed (seq y). > (pop coll) works, (pop seq) does not. The fact that lists happen to act as a coll her

[ANN] eq - A command line tool for edn

Hi! I've been working on a command line tool for edn processing and pretty printing. The project is available at https://github.com/jonase/eq and it is heavily inspired by jq (https://stedolan.github.io/jq/). Eq could be a very useful tool if you're working a lot with edn data (for example via

Re: instrumenting clojure.core

That looks great already. I'm also interested in what the official workflow for adding specs to core is going to be and whether contributions are desired. The last example seems like it could be better because the user has to infer how identity was called within map. So what we'd want is a cod

Re: Bug (in Clojure 1.5): (fn [& xs] (pop xs)) throws ClassCastException clojure.lang.ArraySeq cannot be cast to clojure.lang.IPersistentStack

On Sunday, June 12, 2016 at 2:28:05 AM UTC-4, Alex Miller wrote: > > > > On Sunday, June 12, 2016 at 1:15:23 AM UTC-5, Fluid Dynamics wrote: >> >> >> All of that is very interesting, but then, by your own arguments (pop >> (seq '(1 2 3))) should *not* work. >> > > From you prior post, I think you

instrumenting clojure.core

Yeah, I've been working on parts of this and there will be more to say in the future. -- 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 - pleas

instrumenting clojure.core

Is there an effort to write specs for Clojure's core namespaces? Apologies if this has already been addressed. I've been tinkering with trivial (and probably wrong) fdefs on clojure.core/map and clojure.core/identity. It seems that the spec exception messages are way better than what we have now.