Re: Clojure community survey 2016 results

Thanks for the survey! I think the size distribution for the academic and government/military categories might be due to different respondents deciding how to disambiguate the question in different ways. For example, everyone who works for the U.S. government works in an organization of the

Re: A problem about position of function used by binding

@Matching Socks, thank you very much. -- 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 members are moderated - please be patient with your first post. To

Re: A problem about position of function used by binding

There is a manual! https://clojure.org/reference/documentation - see especially under Vars and Compilation. -- 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

Re: When did this start? java.lang.IllegalAccessError cond* does not exist nippy

> I strongly recommend disabling aot compilation entirely, and if you are > going to aot compile, regularly delete target/. Thank you. I've done so and that seems to help. On Tuesday, February 7, 2017 at 5:44:50 PM UTC-5, red...@gmail.com wrote: > > definitely turn on >

Re: When did this start? java.lang.IllegalAccessError cond* does not exist nippy

> I’ll note that if you’re using the com.taoensso libraries, it pays to make sure you keep them > all in sync because they change a lot H. First of all, this worked, so you are right. Second of all, I am not sure I understand why this worked. I have run into this problem with Ruby and

Re: When did this start? java.lang.IllegalAccessError cond* does not exist nippy

Kevin’s provided some solid advice on the AOT stuff. I’ll note that if you’re using the com.taoensso libraries, it pays to make sure you keep them all in sync because they change a lot (that’s both good and bad), and it’s definitely worth using :exclusions fairly liberally to avoid transient

Re: When did this start? java.lang.IllegalAccessError cond* does not exist nippy

definitely turn on https://github.com/technomancy/leiningen/blob/master/sample.project.clj#L81 :pedantic? :abort and resolve the issues lein deps :tree shows you. given that you are aot compiling, but have implicit clean disabled, my guess is you compiled the project once using a version of some

Re: When did this start? java.lang.IllegalAccessError cond* does not exist nippy

Sorry about that. Here is the whole of my project.clj. It is a fairly small app. (defproject csv-to-dynamodb "1.0" :description "Takes a Super company import file, of CSV format, and stores the data in DynamoDB, using the company_name as the sharding key" :url

Re: When did this start? java.lang.IllegalAccessError cond* does not exist nippy

You’ll need to provide a bit more detail than that – what are your project’s dependencies, for example? (if you’re depending on any snapshots or generic “RELEASE” / “LATEST” versions, those could give you different versions) Sean On 2/7/17, 1:31 PM, "Laws"

When did this start? java.lang.IllegalAccessError cond* does not exist nippy

Two months ago I could run "lein uberjar" and my project compiled. Then I had to focus on other things for 2 months. Then today I come back to it, change one line of code, and run "lein uberjar". I get: java.lang.IllegalAccessError: cond* does not exist, compiling:(nippy.clj:1:1) Exception in

Re: Clojure community survey 2016 results

On 2/7/17, 11:01 AM, "Erik Assum" wrote: > You say 2,420 people took the survey this year. How does that compare to > previous years? The blog post says “This year we held steady in our response rate as 2,420 of you took the time and

Re: Clojure community survey 2016 results

Thanks! You say 2,420 people took the survey this year. How does that compare to previous years? Erik. -- i farta > Den 7. feb. 2017 kl. 19.05 skrev Alex Miller : > > Results and analysis are available here: > >

Clojure community survey 2016 results

Results and analysis are available here: http://blog.cognitect.com/blog/2017/1/31/state-of-clojure-2016-results Many thanks to all that responded! Alex -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to

Re: clojure.spec s/keys map key with alternative definitions in same namespace

>From my perspective, there are two specs. I'm not trying to mash them together, however I would like to use the appropriate spec with the same keyword in maps, in different contexts. It wouldn't be an issue if the contexts were in separate namespaces. It's only an issue because the two specs

Re: clojure.spec s/keys map key with alternative definitions in same namespace

Spec names are intended to have enduring global semantics. So the notion of the same spec name having different semantics at different times seems to be at odds with that. In general, it's often helpful to think about all the possible values that an attribute will have - that's the true spec.

Re: named? predicate?

In 1.9 there is a new ident? function which covers keywords and symbols. If you want to include strings, you would have to make that yourself though. On Tuesday, February 7, 2017 at 9:44:55 AM UTC-6, Dave Tenny wrote: > > I've occasionally wanted this and haven't found it. > > (defn named? >

clojure.spec s/keys map key with alternative definitions in same namespace

Let's say I have these definitions for a "job" record I'm managing, perhaps in a database. (s/def ::job-status #{:in-progress :completed}) (s/def ::user-id (s/and integer? #(>= % 0))) (s/def ::job-id integer?) (s/def ::coercible-job-type (s/and named? #(not (empty? (name %) (s/def

named? predicate?

I've occasionally wanted this and haven't found it. (defn named? "True if object is compatible with the 'name' function. There must be a clojure built-in to do this but I haven't figured it out yet." [x] (or (string? x) (keyword? x) (symbol? x))) Note that simply doing

Re: Clojure.spec, maps, restrict valid keywords, easier way?

Bruce Hauman has done some work in this area both in figwheel and in a branch of leiningen. Basically, if I understand correctly, he looks for misspelled keywords in configuration maps by taking the levenstein distance between expected, valid, keywords and non-matching keywords in the