Re: Is there a standard name for this transducer? Or a more idiomatic way to do it?

looks like a variation of partition-by On 09/14/2016 07:16 PM, Marshall handheld Flax wrote: > This looks like a standard thing you might want to do with a transducer: > accept a stream of inputs and statefully group them into a stream of > varying-length vectors. A typical example might be to

Is there a standard name for this transducer? Or a more idiomatic way to do it?

This looks like a standard thing you might want to do with a transducer: accept a stream of inputs and statefully group them into a stream of varying-length vectors. A typical example might be to accept a series of bowling throws and emit them grouped into bowling frames. So you have a

[CfP] :clojureD 2017

Dear Clojure-community, Please let me bring the current call for proposals for the next iteration of the German clojure conference in Berlin, the :clojureD, to your attention: http://www.clojured.de/call-for-proposals/ We call to send us talks for the upcoming :clojureD conference 2017.

Re: Make core.spec value printing more customisable.

Anyone with a free account can create issues in Clojure's JIRA tracker. Just go to the link below, and if you see a "Log In" link near the top right of the page, click it and create an account on the next page that appears. http://dev.clojure.org/jira/browse/CLJ Andy On Wed, Sep 14, 2016

Re: Make core.spec value printing more customisable.

I've looked at this a bit too. As you mention you can use *print-length* and *print-level* to affect this and that does work. I looked into setting these inside spec to some fixed value but that would take away control from the user. I didn't look at creating new dyn vars specifically for this,

Re: clojure.spec - Using :pre conditions (or not)?

Another option that has been added since the guide was written is s/assert which seems closer to what you're suggesting. (defn name [user] {:pre [(s/assert :common/user user)]} (-> user :user/name)) ;; need to enable assertion checking - this can also be enabled globally with system

Make core.spec value printing more customisable.

Since I couldn't find a more appropiate channel to submit issues such as this one (no github issue tracker and JIRA seems to be only for contributors), I'm submitting it to the mailing list. I find myself most of the time using core.spec for big (but still displayable) data structures. They

clojure.spec - Using :pre conditions (or not)?

(ns spec-test.core (:require [clojure.spec :as s])) (s/def :user/name string?) (s/def :common/user (s/keys :req [:user/name])) ; first version of name (using :pre) (defn name [user] {:pre [(s/valid? :common/user user)]} (-> user :user/name)) ; This statement works ok and returns "Elon":

Re: clojure.spec origin story

>From clojure.spec - Rationale and overview : Almost nothing about spec is novel. See all the libraries mentioned above, RDF , as well as all the work done on various contract systems, such as Racket’s

Call for Contributions: BOB 2017 - Berlin, Feb 24, 2017

Clojure contributions very welcome at BOB! BOB Conference 2017 "What happens when we use what's best for a change?" http://bobkonf.de/2017/en/cfp.html Berlin, February 24 Call for Contributions Deadline: October 30, 2016 You are

Re: Lym - written by clojurescript and react native is on apple store

Cool, thanks =) On Wed, Sep 14, 2016 at 12:32 AM Tienson Qin wrote: > Hi Michael, > There are still some minor works to release the android, have to port > actionsheet from Ios to Android. > They are using the same cljs codebase. > Not too much challenges to get both

Re: Lym - written by clojurescript and react native is on apple store

Hi Michael, There are still some minor works to release the android, have to port actionsheet from Ios to Android. They are using the same cljs codebase. Not too much challenges to get both platforms work. On Wed, Sep 14, 2016 at 3:02 PM Michael Blume wrote: > I see an

Re: Lym - written by clojurescript and react native is on apple store

I see an Android app in the tree, is it working too? is it using the same cljs codebase were there any challenges getting both platforms to work? On Tue, Sep 13, 2016 at 10:24 PM Tienson Qin wrote: > Just release that, > https://github.com/tiensonqin/lymchat > > > On