Because in my app , it is clearer from a semantic point of view, it is clearer
as the value stands for a question asked to the user.
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the
There is no protocol for truthiness, which is what you want. nil and false
are false, everything else is true.
Even if there were a protocol for truthiness, you could not use :yes and :no
(keywords), you would have to create your own custom type and implement the
protocol on it. (Think about
Boolean is not a protocol. It is a native datatype, just like in Clojure.
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
ClojureScript group.
To unsubscribe from this
On Thursday, January 15, 2015 at 5:08:27 PM UTC+1, Yehonathan Sharvit wrote:
Because in my app , it is clearer from a semantic point of view, it is
clearer as the value stands for a question asked to the user.
How about
(ns my-ns.util)
(def YES true)
(def NO false)
(ns my-ns
(:use
Just to be clear, Clojure should be read in a big tent way here to include
ClojureScript and anything Clojure-related of course. ClojureScript talks
desired!!
Alex
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15.01.2015 12:57, gvim wrote:
Here is a Clojurescript database connection in NodeJS and below it
the JS I ported it from. 2 questions:
1. I believe core.async is the way instead of replicating NodeJS
nested callbacks. What is the equivalent
