New blog post: about Clojure's syntax

Reflecting on Clojure's syntax and its implications: http://alvalval.github.io/posts/2018-01-06-so-yeah-about-clojures-syntax.html Feedback welcome! -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@goo

Re: core.async consumer + producer working by chunk?

https://dev.clojure.org/jira/browse/ASYNC-210 > On Jan 6, 2018, at 12:11 PM, Brian J. Rubinton > wrote: > > Thanks! I will. Just signed the CA. > > > On Sat, Jan 6, 2018, 12:10 PM Alex Miller > wrote: > > > On Sat

Re: core.async consumer + producer working by chunk?

Thanks! I will. Just signed the CA. On Sat, Jan 6, 2018, 12:10 PM Alex Miller wrote: > > > On Saturday, January 6, 2018 at 10:56:06 AM UTC-6, Brian J. Rubinton wrote: >> >> Alex - it makes sense to me that the buffer temporarily expands beyond >> its normal size with the content of the expanding

Re: core.async consumer + producer working by chunk?

On Saturday, January 6, 2018 at 10:56:06 AM UTC-6, Brian J. Rubinton wrote: > > Alex - it makes sense to me that the buffer temporarily expands beyond its > normal size with the content of the expanding transducer. What does not > make sense to me is the buffer also accepts puts even though its

Re: core.async consumer + producer working by chunk?

Typo — I meant to say the channel executes puts during a take! even though the buffer is full before executing the puts. This is clearer in code (please see the gist). > On Jan 6, 2018, at 11:55 AM, Brian J. Rubinton > wrote: > > Alex - it makes sense to me that the buffer temporarily expands

Re: core.async consumer + producer working by chunk?

Alex - it makes sense to me that the buffer temporarily expands beyond its normal size with the content of the expanding transducer. What does not make sense to me is the buffer also accepts puts even though its buffer is full. Why would the take! process puts when the channel's buffer is full?

Re: core.async consumer + producer working by chunk?

On Saturday, January 6, 2018 at 10:27:20 AM UTC-6, Rob Nikander wrote: > > > On Jan 5, 2018, at 8:01 PM, Gary Verhaegen wrote: > >> What about simply having the producer put items one by one on the channel? > > > I will do that. My current producer is doing too many other things, but if > I bre

Re: core.async consumer + producer working by chunk?

On Jan 5, 2018, at 8:01 PM, Gary Verhaegen wrote: > What about simply having the producer put items one by one on the channel? I will do that. My current producer is doing too many other things, but if I break it up into separate threads or go blocks for each work queue, then that should wor

Re: [ANN] Git Deps for Clojure!

> On Jan 6, 2018, at 5:43 AM, Khalid Jebbari wrote: > > Great news, great work ! Soon running Clojure will be dead easy. > > 2 questions : > - where do dependencies get downloaded ? `~/.m2` ? It depends on the procurer > (mvn/git/etc.) It depends. Maven deps go to .m2, git deps go to .gitlib

Re: core.async consumer + producer working by chunk?

Rob - I’d go with Gary's approach, which essentially moves the splitting up of the chunk of results from the core.async channel’s transducer to the producing function. You can do that using a channel with a fixed buffer of 50 and >!!. As long as the next db query is blocked until each of the res

Re: [ANN] Git Deps for Clojure!

Great news, great work ! Soon running Clojure will be dead easy. 2 questions : - where do dependencies get downloaded ? `~/.m2` ? It depends on the procurer (mvn/git/etc.) - does it work for Cljs ? What does it mean for Cljs ? -- You received this message because you are subscribed to the Googl

Re: [ANN] Integrated development environment for visual creation and simulation of spatial processes

This project is very interesting. Have a play on this. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog: http://stardiviner.github.io/ On Sat, Jan 6, 20

Re: [ANN] Integrated development environment for visual creation and simulation of spatial processes

New examples screencasts. Full list of screencasts (to be continued): 1. Collision 2. Get started: Simple scenario 3. Get started: New project 4. Get started: Object Mission