user=> (doc read-string)
-
clojure.core/read-string
([s])
Reads *one* object from the string s
nil
(emphasis on *one* by me)
one object from ":a(" = :a; ":a)" = :a; "( … " = fail; ")…" = fail. (remember
whitespace in front of a paren doesn't matter)
Have fun.
From: noa
$ lein new replbuiltin && cd replbuiltin
$ sed -Ee 's,.0",.0"][org.clojure/tools.nrepl "0.2.2",' < project.clj > p
&& mv -f p project.clj
$ lein deps
$ cat < src/replbuiltin/core.clj
(ns replbuiltin.core
(:use [clojure.tools.nrepl.server :only [start-server stop-server]]))
(defn foo [x] x)
(def
$ lein search clojurescript
Searching over Artifact ID...
== Showing page 1 / 2
[org.clojure/clojurescript "0.0-927"] ClojureScript compiler and core
runtime library.
(...)
[org.clojure/clojurescript "0.0-1576"] ClojureScript compiler and core
runtime library.
[org.clojure/clojurescript "0.0-1586"
Obviously it helps to make sure the dependencies you are using are named with
the exact snapshot version.
The biggest time-saver for me though is convincing lein to not do the
dependency dance all the time. I'm surprised though to see that you are
dependency checking at all though. Shouldn't you
ps.com [clojure@googlegroups.com] On Behalf Of Sean
Corfield [seancorfi...@gmail.com]
Sent: Friday, September 07, 2012 18:44
To: clojure@googlegroups.com
Subject: Re: edn
On Thu, Sep 6, 2012 at 8:26 PM, Weber, Martin S wrote:
> The question that's left for me is: why vectors and lists? I mean
Stu:
> The rationale appears to be up now, and for my money, it is quite clear: JSON
> not powerful enough, Clojure does too much and is a burden for implementers.
> That said, I won't complain if somebody happens to implement full Clojure
> serialization while implementing edn. ;-)
The question
> Please don't use edn if you don't see the point. I'm not trying to convince
> you or anyone else.
I expect there to be a point, and thus also expect it to be communicatable. If
there wasn't
a point, you wouldn't have chosen to use it in datomic, or create the page. I
feel you haven't
communic
Rich:
> On Sep 6, 2012, at 9:10 PM, Weber, Martin S wrote:
> > which problem other than "NIH" is edn solving? - given it's a subset of
> > clojure's data notation, it's not really native clojure either, so you
> > gotta convert to/fro.
> Of c
which problem other than "NIH" is edn solving? - given it's a subset of
clojure's data notation, it's not really native clojure either, so you gotta
convert to/fro.
So: Why do we need another JSON?
I'm sure you have answers to these questions, possibly answered them before,
but definitely not
On 2012-07-09 18:07 , "Herwig Hochleitner" wrote:
>> (I had written):
>> So is there a way to do it cleaner without resorting to using the
>> map/implementation (detail) form of protocol extension?
>
>Currently, there is no way to get the implementing fns for a
>type-protocol point. I doubt the
Assume we want to memoize a function that is part of a protocol extended
to some user-defined record, like so:
(defprotocol SomeOps (someop [_]))
(defrecord AImp [x] SomeOps (someop [me] (comment magic here)))
one quite heavy-weight way of doing is includes a couple of indirections:
(defn ^:priv
I'm sorry to say, but IMHO you failed to communicate the critical point to
your audience. If your audience keeps failing to grasp the point, and
communicates this failure back by asking the same question..
I do understand the distinction between a collection and a sequence and
something being a co
Meh. Half-assed (mis)reading. Sorry. -Martin
On 2012-03-29 16:23 , "Weber, Martin S" wrote:
>Yeah I don't like that either. Consider (comp vals (partial group-by
>identity)).
>
>On 2012-03-29 16:18 , "David Jagoe" wrote:
>
>>Hi all,
>>I&
Yeah I don't like that either. Consider (comp vals (partial group-by
identity)).
On 2012-03-29 16:18 , "David Jagoe" wrote:
>Hi all,
>I'm sure I'm missing a really simple way of doing this!
>
>Given a sequence like this: [1 2 1 2 1 1 2 1 2 2 2]
>
>partition it to get this: [(1 2) (1 2) (1) (1 2)
I was looking for something akin common lisps |weIrD SymBol!`| already,
too...
On 2012-03-06 15:28 , "Frank Siebenlist"
wrote:
>SoŠ spaces are not allowed in symbol and keyword identifiers according to
>the "spec"Š
>
>although Stu doesn't quote the phrase following the allowed chars, which
>read
Then both Clojure and ClojureScript's `ns` macro should complain about
multiple present (:require ..) or (:use ..) forms at compile-time. At lest
Clojure's `ns` macro doesn't do that on clj-1.3.
Regards,
-Martin
On 2012-03-05 17:15 , "Stuart Sierra" wrote:
>Yes, it is incorrect, in both Clojure
16 matches
Mail list logo
