Clojurists Together wants to fund you to work on your open source Clojure project

[Daniel Compton]

Hi folks

Clojurists Together  is about to award
another round of funding to support open source Clojure projects. *Applications
 close on Wednesday, July
17th, 2019 at 11:59pm PST.*

Clojurists Together is an organisation, dedicated to funding and supporting
open source software, infrastructure, and documentation that is important
to the Clojure and ClojureScript community.

*We plan to fund each project at $3,000 USD/month for 3 months ($9,000 USD
total).* We're still working out exactly how many projects we will be able
to fund this quarter, but it is likely to be at least 2.

Previously we have supported projects
 like Neanderthal, Aleph,
Fireplace, cljdoc, Shadow CLJS, CIDER, Figwheel, clj-http and several more.

We surveyed
 our
members recently and asked them what they wanted us to focus on.

Highly ranked items were:

   - developer experience tools (49%)
   - build tooling (37%)
   - linters (34%)
   - error messages (33%)
   - IDE support (30%)
   - documentation (19%)
   - test tooling (24%)

Our members also mentioned these projects specifically: shadow-cljs, Duct
Framework, Core.typed, CIDER, Clojuredocs, clj-doc, Eastwood, Cloverage,
buddy, clj-kondo, Reagent, re-frame, FIgwheel Main, Cursive, Leiningen,
Calva, Chlorine, Sente, Nippy, Rum, core.async, incanter, clj-pdf.

We encourage open source maintainers to apply
 for funding, especially
if you work on one of the projects or areas that our members highlighted.

If you work at a company that uses Clojure, talk to your engineering
manager about supporting Clojurists Together. We've been able to support
projects thanks to the generosity of our developer and company members
. The more support we have,
the more that we can do to improve things for the entire Clojure community.

Thanks, Daniel.

-- 
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/CAK2UX_j5yApwOK3XDZy%2BXy6Dni7kX_XbLcZx7nuPujNVW6yiCw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: core.async: Unbound channels

[Ernesto Garcia]

Thanks Alex!

Correct, the channel implementation takes care that "transduced" channels 
always pass elements through the transducer and the buffer. Also, a 
FixedBuffer allows running out of limit for those cases, see this example 
with a FixedBuffer of size 1 making space for 4 elements:

(def c (chan 1 (mapcat seq)))
=> #'psdk.hack-config/c

(put! c "hola")
=> true

(-> c .buf .buf)
=> (\a \l \o \h)

However, the blocking semantics of a channel change if a buffer is 
enforced. You can't have a "transduced" channel for which all puts will 
block for a take. Not sure if this is too limiting for any practical case.

For the case of expanding transducers, I am not sure if there would be 
sensible semantics for channel operations without a buffer.

-- 
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/a652870b-59c2-40f9-b4e0-7387e87de204%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.