Thanks, exactly what i needed
On Monday, June 22, 2015 at 1:01:30 AM UTC+3, Sean Corfield wrote:
>
> How about this:
>
> (defmacro matches [value pattern]
> `(is (match ~value ~pattern true :else false)
>(str "(match " ~value " " '~pattern ")")))
>
> (let [a {:x 2}]
>
It would be fun to use core.match to have an easier time testing results
that are hash-maps of different patterns. I'm just having a difficult time
to get failing cases' input values show up in test results:
(use 'clojure.test)
(require '[clojure.core.match :refer [match]])
(defmacro matches [
On Monday, April 13, 2015 at 4:48:28 PM UTC+3, Alex Miller wrote:
>
> I think what you're seeing here makes sense.
>
> On Sunday, April 12, 2015 at 3:39:15 PM UTC-5, whodidthis wrote:
>>
>> Are there any thoughts on code like this:
>>
>> #_
>
t;
> On Sunday, April 12, 2015 at 3:39:15 PM UTC-5, whodidthis wrote:
>>
>> Are there any thoughts on code like this:
>>
>> #_
>>
>
> This says to ignore the next read form
>
>
>> #?(:cljs (def unrelated-1 nil))
>>
>
> Th
Not to mention how compact even interactive cljs development is in
comparison.
I made a small example on using om with the figwheel like
cljs-reload.
https://github.com/om-cookbook/om-cookbook/tree/master/recipes/boot-setup
On Wednesday, December 17, 2014 7:31:52 PM UTC+2, Ivan L wrote:
>
> cl
Very nice one, Dom.
Bidirectional routes are indeed especially important to render and dispatch
routes in Om etc. In secretary its a bit awkward since you have to write stuff
like (defroute front-page "/" [] :front-page) and then a separate thingie for
matching the keywords back to the routes.