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 -
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
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
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
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
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,
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
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
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
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
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
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
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
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
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)
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
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
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
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"
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
20 matches
Mail list logo
