Re: Help with idiomatic clojure.

Doh - I obviously hadn’t had enough coffee that early in the morning :-). > On 13 Nov 2015, at 01:47, Chris Murphy wrote: > > > I think true and false should be swapped around, because seq and empty? are > opposites, seq meaning it is not empty. > > On 13/11/2015 8:08 AM,

A call for an idiomatic rendering of Clojure EDN in info/error messages

Hi all, Can we, the community agree a consistent way of rendering Clojure EDN when we report it in info or error. For example, given the EDN "2" (i.e. a string containing a single character 2) I have seen various libraries render it as: - 2 - "2" - ["2"] - [2] - (2) - '"2"' I would

Re: A call for an idiomatic rendering of Clojure EDN in info/error messages

For what it’s worth, I like to use matching `backquotes` as a meta-syntax. (defn expected [exp was] (format "Expected `%s` but was `%s`" (pr-str exp) (pr-str was))) (println (expected 2 "2")) ;=> Expected `2` but was `"2"` > On Nov 13, 2015, at 6:55 AM, Colin Yates

Re: A call for an idiomatic rendering of Clojure EDN in info/error messages

+1 for backquotes, as I understand then without needing to think about it because of markdown. (I use them in docstrings and commit messages and error messages, too.) On Nov 13, 2015 10:26 AM, "Steve Miner" wrote: > For what it’s worth, I like to use matching `backquotes`

Re: A call for an idiomatic rendering of Clojure EDN in info/error messages

As a newbie, a red warning flag pops up when I see a back tick. :-) -- 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

[ANN] org.clojure/tools.namespace "0.3.0-alpha2"

tools.namespace — Parse ns declarations from source files, extract their dependencies, build a graph of namespace dependencies within a project, update that graph as files change, and reload files in the correct order. https://github.com/clojure/tools.namespace Leiningen-style dependency:

Re: A call for an idiomatic rendering of Clojure EDN in info/error messages

I recall Google uses vertical bars in ObjC comments for similar purposes, as stated in their style guide: Use vertical bars to quote variable names and symbols in comments rather than quotes or naming the symbol inline. This helps eliminate ambiguity, especially when the symbol is a common

Re: A call for an idiomatic rendering of Clojure EDN in info/error messages

This. Confusing for the rubyists but hey :-). > On 13 Nov 2015, at 17:13, Yuri Govorushchenko wrote: > > I recall Google uses vertical bars in ObjC comments for similar purposes, as > stated in their style guide: > > Use vertical bars to quote variable names and symbols

Re: A call for an idiomatic rendering of Clojure EDN in info/error messages

+1 for no special markup, +1 for backquotes, -1 for underscore, -1 for pipe char. On Fri, Nov 13, 2015 at 7:18 PM, Colin Yates wrote: > This. Confusing for the rubyists but hey :-). > > On 13 Nov 2015, at 17:13, Yuri Govorushchenko > wrote: > > I

Re: A call for an idiomatic rendering of Clojure EDN in info/error messages

On Fri, Nov 13, 2015 at 5:47 AM, Colin Yates wrote: > Really, I don’t mind - I would just like consistency :-) > > One argument for the right delimiter of some sort is that it is > unambiguous and therefore nobody can misinterpret it. If you were > unfamiliar with a

Re: A call for an idiomatic rendering of Clojure EDN in info/error messages

Hi Ben, I’m pretty sure we are all on the same page that rendering a string with a single character of 2 is “2”. Regarding not needing a delimiter: if everybody everywhere signed up to this then yes, I agree - no delimiter is necessary. Until that becomes true then I still think a delimiter

Re: JDBC Rollbacks and Exceptions

Andy Chambers wrote on Thursday, November 12, 2015 at 10:49 PM: I threw up an example repo demonstrating the type of test I'd like to be able to write somehow. Maybe I'm just trying to test something that should be tested in other ways. https://github.com/cddr/jdbc-demo As Andrey indicates,

core.async mult "damaged" on reload

I put a core.async/mult instance in a map structure in a map. When i do load-file ... (from La Clojure in IntelliJ) the structure with the object instance is still there, but it isn't possible to use. I get: > CompilerException java.lang.IllegalArgumentException: No implementation of > method:

[ANN] test.check 0.9.0

I'm happy to announce the release today of version 0.9.0 of test.check, the QuickCheck-inspired property-based testing library. The changes in this release are a new minimum required version of Clojure (1.7) and a handful of new generators. Clojure 1.7 is required now as the test.check

Re: [ANN] Pipes 0.1.1 - chain processes, shell commands and threads via pipes

Looks nice! Alan On Fri, Nov 13, 2015 at 5:56 AM, Marcin Bilski wrote: > Home: https://github.com/bilus/pipes > > If you ever used Un*x pipes > > ``` > $ ls | grep .clj > ``` > > then this library gives you a power to do this in Clojure and a lot more. > > You can use

Re: [ANN] Pipes 0.1.1 - chain processes, shell commands and threads via pipes

Just a bit of history from which you might derive some inspiration for your pipe metaphors in Clojure, the scheme shell. Main site: http://scsh.net/ Docs on various constructs, including process I/O operators: http://scsh.net/docu/html/man-Z-H-1.html#node_toc_start On Friday, November 13,

Re: A call for an idiomatic rendering of Clojure EDN in info/error messages

I would that the existing format of pr-str would work, no?. I often structure Exception error strings like: foo-service: bad value=2 foo-service: bad value="2" Does that not keep it unambiguous? Alan On Fri, Nov 13, 2015 at 10:59 AM, Colin Yates wrote: > Hi Ben, > > I’m

Re: A call for an idiomatic rendering of Clojure EDN in info/error messages

+1 for | -- 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

Re: A call for an idiomatic rendering of Clojure EDN in info/error messages

A pair of curly brackets with a single value isn't part of the grammar either, and I think reads better than _ On Nov 13, 2015 8:47 AM, "Colin Yates" wrote: > Really, I don’t mind - I would just like consistency :-) > > One argument for the right delimiter of some sort is

Re: A call for an idiomatic rendering of Clojure EDN in info/error messages

That is too close to a literal set or literal map for my tastes… > On 13 Nov 2015, at 14:30, Gary Trakhman wrote: > > A pair of curly brackets with a single value isn't part of the grammar > either, and I think reads better than _ > > On Nov 13, 2015 8:47 AM, "Colin

Re: A call for an idiomatic rendering of Clojure EDN in info/error messages

Hi Colin, Why not just "2"? On Fri, Nov 13, 2015 at 1:55 PM, Colin Yates wrote: > Hi all, > > Can we, the community agree a consistent way of rendering Clojure EDN when > we report it in info or error. For example, given the EDN "2" (i.e. a > string containing a single

Re: Help with idiomatic clojure.

I think I like 'seq' better than 'empty?'.I'm sure my opinions will firm up after writing some more clojure. > Also, in no-errors branch you probably want to return status: 200? I picked the function where I knew there was a better way. This validation function is called from this bit

Re: Help with idiomatic clojure.

Another tip when using seq then: cljs.user=> (or (seq [1 2 3]) false) (1 2 3) cljs.user=> (or (seq []) false) false cljs.user=> > On 13 Nov 2015, at 14:09, Brian wrote: > > I think I like 'seq' better than 'empty?'.I'm sure my opinions will firm > up after

[ANN] Pipes 0.1.1 - chain processes, shell commands and threads via pipes

Home: https://github.com/bilus/pipes If you ever used Un*x pipes ``` $ ls | grep .clj ``` then this library gives you a power to do this in Clojure and a lot more. You can use streams to chain any number of shell commands, processes and Clojure functions to process the streams on the fly.

Define new defn, lein uberjar succeeds to compile but lein run fails

I defined my own defn in the namespace mwm. My new code looks like this (mwm/defn foo [x] ...) Everything was fine as long as it was called defn2, but after renaming it to defn and refering to the original defn using clojure.core/defn, only "lein uberjar" works. When I run "lein run",

Re: A call for an idiomatic rendering of Clojure EDN in info/error messages

Really, I don’t mind - I would just like consistency :-) One argument for the right delimiter of some sort is that it is unambiguous and therefore nobody can misinterpret it. If you were unfamiliar with a validation library and it reported [:a :b :c must be “2”] you _could_ interpret that as