Re: Using :clojure.spec.alpha/invalid inside clojure.core macros throw exception
This is a known issue, see https://clojure.atlassian.net/projects/CLJ/issues/CLJ-1966 -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/clojure/20190918194827.GA15694%40azadi.
[no subject]
I’m an email user. For some reason official announcements (by Alex Miller) don’t get sent out via email, they only appear in the Google Groups web interface. Replies (and all other messages) do land in my inbox, though. Something wrong with your email Alex, or is it Google Groups? -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/clojure/20190718112053.GA12047%40azadi. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
[ANN] tools.deps.alpha 0.6.496 and clj 1.10.0.442
Nice, thank you, Alex! By the way, I am no longer getting email notifications from Jira, though nothing has changed on my end … just to let you know. -- David -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Can someone explains the difference between print-method and print-dup once and for all?
On 10/08/18 06:33, Didier wrote: > Thanks David. So if I need to extend edn to serialize custom types, I should > extend print-method? And have it switch on print-readably? Where when true, > prints a reabale edn literal #x/y ... for example, otherwise it prints as > standard? > > Would that be the correct way? Sounds reasonable to me. There is an old ticket which has pointers to some relevant discussion I think: https://dev.clojure.org/jira/browse/CLJ-1201 -- David -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Can someone explains the difference between print-method and print-dup once and for all?
If your goal is to produce edn, go with pr/prn/*print-readably*, not
print-dup. print-dup output often cannot be read as edn:
(print-dup {:k "v"} *out*)
;; #=(clojure.lang.PersistentArrayMap/create {:k "v"})
--
David
--
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 to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Forward-declare a spec before use?
I am running into an issue where a spec is aliased before it is defined. (s/def :x/foo :x/missing) ; throws :x/missing is only defined later. Some of the spec macros do allow referring to non-existent specs, for example s/nilable: (s/def :x/foo (s/nilable :x/missing)) ; fine, resolution delayed Is it possible to somehow forward-declare a spec to make this work? (Of course, if I were writing these specs by hand I could just fix the order, but the specs are being generated, so that is not so easy.) -- David -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] clojure tools 1.9.0.315, tools.deps.alpha 0.5.342
Ah, I didn’t think of checking other branches, thank you both. -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] clojure tools 1.9.0.315, tools.deps.alpha 0.5.342
On 23/01/18 21:37, Alex Miller wrote: > clojure tools 1.9.0.315 is now available in brew and > via https://clojure.org/guides/getting_started > > Highlights: > > * NEW -Stree to print dependency tree > * NEW -Sdeps to supply a deps.edn on the command line as data > * FIX bug with git deps using :deps/root writing File objects to libs > files These changes are missing on the master branch at https://github.com/clojure/brew-install? Also, in the help text the ‘-Sdeps’ and ‘-Stree’ lines use spaces instead of tabs which makes the output a bit less tidy. -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
How to spec reducible collections
Suppose I want to spec a function like run!. run! takes an ifn? and a ‘coll’, where the coll argument may be any reducible collection (so coll? is really not the right choice, nor is seqable?). I tried to construct a spec for reducible collections but failed. The protocol used in reduce is extended to java.lang.Object, so (satisfies? CollReduce coll) will never produce a useful answer. How does one spec a function like run!? -- David -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Clojure CLI tool fails to resolve weird transitive dependencies.
Hm, looks like this is an open issue: https://dev.clojure.org/jira/browse/TDEPS-12 -- David -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Clojure CLI tool fails to resolve weird transitive dependencies.
On 11/12/17 20:47, Jonathan Fischer wrote:
> com.badlogicgames.gdx/gdx {:mvn/versin "1.9.6"}
Typo?
--
David
--
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 to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Unexpected performace of transducers
Jiacai – I saw you updated the gist. Just in case it passed you by: performance profits from the source collection being reducible. So pouring ‘dataset’ into a vector beforehand should speed up the processing quite a bit. Also, I think the transducer version should always be faster, no matter the size of the source collection (no threshold). -- David -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Using ring, jetty plugin: No reader function for tag object
Perhaps try downgrading Leiningen to 2.7.1: lein upgrade 2.7.1 See https://github.com/technomancy/leiningen/issues/2328. -- David -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Couplet 0.1.0 – Unicode code points support for Clojure
Clojure strings are made up of chars, but the conventional unit of digital texts is Unicode characters (‘code points’). Effective work at the boundary requires a library – • a reducible seqable representation of strings as code points • supports fold • transducer for converting chars to code points • copy-pastably small https://github.com/glts/couplet Thank you, -- David -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Help ship Clojure 1.9!
Hello Stu, On 02/10/17 16:55, Stuart Halloway wrote: > Spec will be in alpha for a while. That is part of the point of it being > a separate library. Can you say more about what problems this is causing? I don’t have any stakes in this so it’s better if I withdraw my question. I was (still am) a bit worried that the alpha namespaces of spec are going to be visible for all users (tooling?) via error messages. I also have difficulties imagining how the migration from spec.alpha to spec will work (impacts all libraries using it?) … I may just be confused. -- David -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Help ship Clojure 1.9!
On 28/09/17 16:00, Stuart Halloway wrote: > Clojure 1.9 has been quite stable throughout the alpha period, and we > now hope to release after a very short beta. Please test your existing > programs on the latest beta (see below), and respond on this thread ASAP > if you discover anything you believe to be a regression. Will there be a non-alpha release of spec together with Clojure 1.9? Some newer libraries have statements like ‘in alpha while Clojure 1.9 is in alpha’, but what they actually seem to mean is that they’re in alpha while spec is in alpha. I think a proper release of spec (namespaces without the word ‘alpha’) sometime soon would be very welcome. -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Obtaining the predicate of a spec
On 22/09/17 23:19, Beau Fabry wrote: > Not sure if I'm being glib here but #(s/valid? ::pm-hours %) returns a > predicate that has the exact same results as #(s/int-in-range? 12 24 %) Fair, but I was thinking specifically of those situations where you want to bypass the spec registry, say where you really need the performance of the predicate, not the spec. -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Should the completion arity of a stateful transducer reset state?
On 22/07/17 22:02, Timothy Baldridge wrote: > Once a transducer is completed it should never be called again. Thank you, Timothy, this was probably obvious but I don't remember reading it anywhere so this really helped. David -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How is this code to create a stateful lazy sequence?
Perhaps you want to study the implementation in Medley, those are always very good quality: https://github.com/weavejester/medley/blob/254989ed3de83c30ce0101d66c7ce1b6ee257b4d/src/medley/core.cljc#L173 David -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Should the completion arity of a stateful transducer reset state?
Hello all, I found an edge case where stateful transducers in core differ in whether they reset or clear state in the completion arity (partition-all) or don’t (take). Given the two transformed reducing functions (def conj-partitioning-all-3 ((partition-all 3) conj)) (def conj-taking-3 ((take 3) conj)) when performing transduction with those reducing functions twice in a row, one yields the same result twice, the other doesn’t. (transduce identity conj-partitioning-all-3 [] (range 10)) ;; => [[0 1 2] [3 4 5] [6 7 8] [9]] ;; => [[0 1 2] [3 4 5] [6 7 8] [9]] (transduce identity conj-taking-3 [] (range 10)) ;; => [0 1 2] ;; => [] Question: which behaviour is the one I should emulate in my own transducers? Thank you, David -- 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 to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
