Re: How to restrict the number of test with stest/check

Thanks! -- 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 unsubscribe from this group, send email

Re: Is this behavior of clojure.core/pr a bug?

Er, I mean "built-in reader macro dispatch". On Thursday, August 4, 2016 at 1:14:16 AM UTC, Blake Miller wrote: > > You're right, Dan. Having mulled it over a little more, it's not clear to > me why there ought to be any pure Clojure data (no Java objects) that > cannot be serialized as EDN.

Re: Is this behavior of clojure.core/pr a bug?

You're right, Dan. Having mulled it over a little more, it's not clear to me why there ought to be any pure Clojure data (no Java objects) that cannot be serialized as EDN. Emitting a #keyword reader literal for this edge case would make sense to me. -- You received this message because you

Re: Is this behavior of clojure.core/pr a bug?

Why not just have #keyword and #symbol reader syntax tags that pr could produce for situations like this? It's really preferable that pr not throw exceptions, but it's also quite an abomination that it silently produces bad edn. On Wednesday, August 3, 2016, Blake Miller

Re: Is this behavior of clojure.core/pr a bug?

Thanks for that concise explanation, Sean. It makes sense to me that not all valid Clojure data is serializable. There's still something about this that doesn't quite make sense to me, though: clojure.core/pr, rather than throwing an exception when asked to serialize an instance of

Re: Is this behavior of clojure.core/pr a bug?

You can programmatically create keywords that are illegal as literals, i.e., will not be accepted by the reader. This is not a fault of clojure.core/pr – if it is given a value that uses legal (readable) keywords, its result will indeed be readable by clojure.core/read-string. You can

Re: Is this behavior of clojure.core/pr a bug?

Thanks, Timothy. I'll give transit a try. -- 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

Re: Is this behavior of clojure.core/pr a bug?

The docstring of clojure.core/pr https://github.com/clojure/clojure/blob/clojure-1.7.0/src/clj/clojure/core.clj#L3552-L3555 actually says (in lieu of a formal EDN specification?) "pr and prn print in a way that objects can be read by the reader" ...and the example I showed appears to violate

Re: Is this behavior of clojure.core/pr a bug?

I highly suggest using transit. It's much faster and formally specified. https://github.com/cognitect/transit-format It's issues like this that caused the creation of transit in the first place. On Wednesday, August 3, 2016, Blake Miller wrote: > I have tried this with

Is this behavior of clojure.core/pr a bug?

I have tried this with Clojure 1.7.0, 1.8.0 and 1.9.0-alpha10 (clojure.core/read-string (clojure.core/with-out-str (clojure.core/pr (clojure.core/keyword "A valid keyword" ;; => :A This just seems wrong. It's valid to have an instance of clojure.lang.Keyword with a space in its name.

Re: Frustrations so far

Hi Peter, The latest release of Datomic (0.9.5390) includes the addition of the Log API for memory-backed databases. https://groups.google.com/d/topic/datomic/QLdZ_WePR5A/discussion. Hope this and some of other items on this thread will combine to improve your experience with Clojure. Regards,

Re: How to restrict the number of test with stest/check

As the docstring for check notes: "The opts map includes the following optional keys, where stc aliases clojure.spec.test.check: ::stc/opts opts to flow through test.check/quick-check :genmap from spec names to generator overrides" So the opts map would be like: (stest/check `myfunc

ANN: EuroClojure Call for Presentations end this Friday!

There are two more days to submit a talk to EuroClojure! Here are the details... EuroClojure Event date: October 25-26, 2016 Location: Bratislava, Slovakia Submission deadline: Friday, August 5 Call for presentations submission link Travel expenses covered:

Re: [ClojureScript] Re: Preparing proposal for presentation on replikativ

@Daniel > I would be very interested in learning about how to use replikativ: > what can and can't it store, when is and isn't it a good fit, > demo/sample code of common and not so common use cases etc > I've looked at replikativ and even went down the "learn lots about > CRDTs" rabbit hole and

Re: ANN: Klipse for Kids

On Wednesday, August 3, 2016 at 6:00:43 AM UTC-5, Yehonathan Sharvit wrote: > > Mars0i, as I see it interactivity is the key for effective learning - both > for kids and adults. > > This is the whole point of Klipse - https://github.com/viebel/klipse. > Ah, very nice. I know about Clojurescript

How to restrict the number of test with stest/check

Hi, (stest/check `myfunc) runs very, very long so i tried (stest/check `myfunc {:num-tests 2}) but unfortunately that does not restrict the number of test. Can anybody help? Kind regards, Burt -- You received this message because you are subscribed to the Google Groups "Clojure" group. To

Re: ANN: Klipse for Kids

Mars0i, as I see it interactivity is the key for effective learning - both for kids and adults. This is the whole point of Klipse - https://github.com/viebel/klipse. By the way, do you have any suggestion about how to make the errors less daunting? On Tuesday, 2 August 2016 20:52:30 UTC+3,

Re: ANN: Klipse for Kids

Thanks JvJ. I've fixed it. On Tuesday, 2 August 2016 22:47:41 UTC+3, JvJ wrote: > > Pretty good. However: In chapter 1, you might want to clear up the fact > that 7*8 is 7 x 8 early on. Kids may not be familiar with the * as a > multiplication symbol. I realize it's explained later, but it's

Re: [ClojureScript] Re: Preparing proposal for presentation on replikativ

I would be very interested in learning about how to use replikativ: what can and can't it store, when is and isn't it a good fit, demo/sample code of common and not so common use cases etc I've looked at replikativ and even went down the "learn lots about CRDTs" rabbit hole and think I have an OK