Thanks to encouragement from Chris I want to continue on the Firebase path
and investigate the pros/cons of storing datoms instead of entities.
I am thinking the schema will be:
{tx: {x1: {user: u1
t: epoch}}
eavt: {e1: {e: 1
a: age
v: 40
t
Stepping back... Clojure's print system has two families of functions - one
for human consumption and one for data. Many kinds of Clojure data print
the same in either mode (strings are one exception).
The human printing is most commonly encountered with functions like
println, print. and str.
Hi,
I am pleased to announce the 0.0.2 release of psq.clj, a Clojure
priority search queue library based on Ralf Hinze's priority search
pennants (see Ralf Hinze, "A Simple Implementation Technique for
Priority Search Queues"):
https://github.com/michalmarczyk/psq.clj
https://clojars.org/psq
Alex, what is the exact difference between pr-str and str (when passing a
single arg)?
On Sun, 20 Nov 2016 at 19:40 Alex Miller wrote:
> pr-str is the companion to read-string
>
> Although, there are many many cases where this round trip will not result
> in the same input. Things like reader ma
pr-str is the companion to read-string
Although, there are many many cases where this round trip will not result in
the same input. Things like reader macros, autoresolved keywords, etc will be
expanded in the reader.
--
You received this message because you are subscribed to the Google
Groups
Nope.
=> (str (read-string "\"foo\""))
"foo"
- James
On 20 November 2016 at 16:53, Yehonathan Sharvit wrote:
>
> Let s be an s-expression in clojure.
>
>
> Is the following assertion always true?
>
> (= (str (read-string s)) s)
>
>
>
>
> --
> You received this message because you are subscrib
Let s be an s-expression in clojure.
Is the following assertion always true?
(= (str (read-string s)) s)
--
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 memb
