Re: Lym - written by clojurescript and react native is on apple store

Just release that, https://github.com/tiensonqin/lymchat On Monday, August 29, 2016 at 6:28:56 AM UTC+8, Gary Schiltz wrote: > > Thanks for making this free! Any chance you are going to release the > source? > > On Sunday, August 28, 2016 at 3:28:57 AM UTC-5, Tienson Qin wrote: >> >> Hi everyone

alpha11 clojure.spec validation for fdef

instrument only checks the :args spec of the function. The higher order function is in the :ret spec so isn't checked. You can use the check function to generate tests that verify the :ret and :fn specs. -- You received this message because you are subscribed to the Google Groups "Clojure" gro

alpha11 clojure.spec validation for fdef

I am trying to write a higher order function in clojure.spec with version 1.9.0-alpha12 and have not been able to get the validation to execute against the returned function. Using the example in the *Higher order functions* section of the clojure.spec guide,

Re: get function

On 9/13/16, 5:02 AM, "Erik Assum" wrote: > you’ll see that `get` accepts an additional argument, the default value, > which e.g. the keyword does not. Just FYI, both the keyword first form and the map first form do accept an additional default argument: boot.user> (:b {:a 1 :b 2} 3) 2 boot.us

Re: core.logic with 1.9.0-alpha12

Filed LOGIC-180 bug with patch. http://dev.clojure.org/jira/browse/LOGIC-180 -- 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

Re: core.logic with 1.9.0-alpha12

It looks like the problem is with the macro -inc. It should quote the internal fn name so that it stays an unqualified symbol during macro expansion. I need to test this a bit as I’m not familiar with this code. I’ll make a patch soon if David doesn’t fix it first. By the way, spec point

Re: get function

The `get` function will accept `nil` as the map argument and return `nil`, but invoking `nil` will throw a NullPointerException. By convention, people use `get` when they don't know what the map argument is, since it might be nil. And we use keywords as functions when they are literals, like (:

Re: core.logic with 1.9.0-alpha12

Oops don't think so. If you have a patch, that would be welcome. David On Tue, Sep 13, 2016 at 3:45 AM, 'Burt' via Clojure < clojure@googlegroups.com> wrote: > Hi, > > with "1.9.0-alpha10" and core.logic "0.8.10": > > (ns lwb.nd.rules > (:refer-clojure :exclude [==]) > (:require [clojure.cor

Re: get function

From https://clojuredocs.org/clojure.core/get you’ll see that `get` accepts an additional argument, the default value, which e.g. the keyword does not. As for getting stuff out of maps, the idiomatic way is (def m {:a 1 :b 2}) (:b m) ;; => 2 There is otherwise a nice discussion about the finer

Functional Programming Jobs across the globe! www.functionalworks.com

Check out our new platform (built in Clojure/Clojurescript), the one stop shop for Functional Programming roles across the globe. Check it out .. www.functionalworks.com -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send

get function

Hi everyone, I am new to Clojure and have been playing around with it for a little while. I have seen that (get [3 2 1] 0) and ([[3 2 1] 0) both return the value 3. Similarly (get {:a 0 :b 1} :b) and ({:a 0 :b 1} :b) return 1. I was wondering if anyone could explain why the get function is usef

core.logic with 1.9.0-alpha12

Hi, with "1.9.0-alpha10" and core.logic "0.8.10": (ns lwb.nd.rules (:refer-clojure :exclude [==]) (:require [clojure.core.logic :refer :all])) => nil with "1.9.0-alpha12" and core.logic "0.8.10": (ns lwb.nd.rules (:refer-clojure :exclude [==]) (:require [clojure.core.logic :refer :all])

[JOB] Full Stack Clojure Engineers at Juji

Juji, Inc. is an early stage startup located in the silicon valley. We work in the area of artificial intelligence, and our platform in alpha release has generated great customer interests, hence we are hiring full stack engineers in both senior and entry level to build out the platform to meet