Re: Unexpected behaviour of transient map

Thanks, that is useful advice. I do think that the docstring for assoc! could be more explicit about the dangers of not using the return value. Given the value placed in experimenting in the REPL it's easy to see how one could be fooled into using assoc! incorrectly. On Friday, 24 November 2

[ANN] Dynadoc, dynamic docs for Clojure(Script)

I'm releasing a new project called Dynadoc which generates a single searchable doc website for everything in your project, including all your dependencies. It supports Clojure *and* ClojureScript. It also lets you create interactive code examples that can be edited from the browser. Currently t

Re: Unexpected behaviour of transient map

I know they aren't "official" Clojure documentation, but the examples and comments at clojuredocs.org are often correct, and even sometimes illuminating. http://clojuredocs.org/clojure.core/assoc! All of the clojuredocs.org pages for transient operations refer to that one for a more full discussi

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

Re: Unexpected performace of transducers

>> Also, I think the transducer version should always be faster, no matter the size of the source collection (no threshold). It's a bit more complicated than that, mostly because transducer pipelines require about 2 allocations per step during creation. Also, most of the performance boost from tra

Re: Unexpected performace of transducers

Chunked seqs are annoyingly fast. :) On Monday, November 27, 2017 at 3:07:10 PM UTC-6, tbc++ wrote: > > >> Also, I think the transducer version should always be faster, no matter > >> the > size of the source collection (no threshold). > > It's a bit more complicated than that, mostly because tr

[ANN] Clojure 1.9.0-RC2

Clojure 1.9.0-RC2 is now available. Try it via - Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.9.0-RC2 - Leiningen: [org.clojure/clojure "1.9.0-RC2"] 1.9.0-RC2 is largely the same as RC1 but has the following changes: - There is a new Maven profile and Ant target in the build t

Re: [ANN] Clojure 1.9.0-RC2

I should also mention that I've re-built the Clojure doc automation process and the Clojure docs have refreshed for the first time in a long while. Most importantly, the 1.9 docs are up to date and now include specs for things that have been spec'ed: https://clojure.github.io/clojure/branch-mas

Re: [ANN] Clojure 1.9.0-RC2

> On 2017-11-27, at 16:17, Alex Miller wrote: > > I should also mention that I've re-built the Clojure doc automation process > and the Clojure docs have refreshed for the first time in a long while. Thanks, Alex! Michael Glaesemann grzm seespotcode net -- You received this message becaus

Re: Grateful Appreciation

Hi! I would also like to express my appreciation for the language and the community. I use Clojure at work and it hits me daily how fun and interesting it is to program in. A big thank you to all developers and maintainers of the core language and all open source libraries. Thanks to all kind peop

[ANN] Dynadoc, dynamic docs for Clojure(Script)

Nice! This will come in very handy. I’ve also been checking out your Nightlight project. Very impressive work. 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 ne

Re: Unexpected performace of transducers

> Also, most of the performance boost from transducers is due to less garbage being created, and some times the heap of the JVM is so large you'll never see much change from switching to transducers. Thanks for this tip. I seldom use transducers in my daily work, and I was convinced transducer

Re: Unexpected performace of transducers

I would say transducers are preferable when: 1) you have reducible collections 2) you have a lot of pipelined transformations (transducers handle these in one pass with no intermediate data) 3) the number of elements is "large" (this amplifies the memory and perf savings from #2) 4) you put to p

Re: [ANN] Clojure 1.9.0-RC2

Great choices on how to present core specs -- really clean & readable. Thanks! On Monday, November

Re: Unexpected performace of transducers

Thanks Alex. Good summary. I think this can be added to https://clojure.org/reference/transducers On Tue, Nov 28, 2017 at 10:54 AM, Alex Miller wrote: > I would say transducers are preferable when: > > 1) you have reducible collections > 2) you have a lot of pipelined transformations (transducer