Validation of prismatic schema

2016-05-16 Thread Peeyush Jain
Hello everyone, I am very new to clojure programming. I have a problem with my schema validation and i have asked the question on stackoverflow. link: http://stackoverflow.com/q/37263775/3639192 . I know it is a very basic question but i have been trying to solve it for

Re: :default catch blocks with core.async and clojurescript

2016-05-16 Thread Kevin Downey
On 05/15/2016 06:39 PM, Kevin Downey wrote: > On 05/14/2016 09:31 PM, cameron wrote: >> I'm having an issue where :default catch blocks are not working in >> clojurescript when in a go block. >> >> The following code prints "a str" as expected: >> >> (prn (try >>(throw "a str") >>

Re: Reflection warning: {} argument can’t be resolved as java.util.Map

2016-05-16 Thread Alex Miller
Thanks! -- 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 unsubscribe from this group, send email

Re: Reflection warning: {} argument can’t be resolved as java.util.Map

2016-05-16 Thread 676c7473
I have opened http://dev.clojure.org/jira/browse/CLJ-1929. -- 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 firs

Re: Reflection warning: {} argument can’t be resolved as java.util.Map

2016-05-16 Thread 676c7473
Another observation: it seems that the type inference stumbles only when there is an overloaded method with the same arity (?): (import 'java.time.format.TextStyle) (let [builder (DateTimeFormatterBuilder.)] (.appendZoneText builder TextStyle/FULL #{})) This is a similar case in th

Re: Reflection warning: {} argument can’t be resolved as java.util.Map

2016-05-16 Thread Nicola Mometto
Actually s/constant/literal/ https://github.com/clojure/clojure/blob/master/src/jvm/clojure/lang/Compiler.java#L3003-L3005 https://github.com/clojure/clojure/blob/master/src/jvm/clojure/lang/Compiler.java#L3057-L3060 https://github.com/clojure/clojure/blob/master/src/jvm/clojure/lang/Compiler.java#

Re: Reflection warning: {} argument can’t be resolved as java.util.Map

2016-05-16 Thread Nicola Mometto
On 16 May 2016, at 15:53, Alex Miller wrote: > > This is kind of an interesting case. From poking at it a bit, the {} is typed > as a IPersistentMap, and IPM does NOT extend java.util.Map (although the > implementations like PersistentArrayMap and PersistentHashMap do via > APersistentMap). >

Re: Reflection warning: {} argument can’t be resolved as java.util.Map

2016-05-16 Thread Alex Miller
This is kind of an interesting case. From poking at it a bit, the {} is typed as a IPersistentMap, and IPM does NOT extend java.util.Map (although the implementations like PersistentArrayMap and PersistentHashMap do via APersistentMap). I think the interesting question is why the type hint is n

Access user created Java package from Clojure

2016-05-16 Thread Michael Rice
I'm working through "Clojure for the Brave and True." Right now I'm focused on Java interop, in particular creating a simple Java package and accessing it from Clojure. My applicable directory structure is listed below along with some code, examples of it executing, and my classpath. For starte

Re: Clojure docstring style

2016-05-16 Thread Phillip Lord
The problem is that the var might not be a var yet. You'd have to re-render code after evaluation. Phil Christopher Small writes: > Seems like this shouldn't be a problem as long as you only try to render a > link if there's actually such a var. This might be a little messier, but > would m

Reflection warning: {} argument can’t be resolved as java.util.Map

2016-05-16 Thread 676c7473
Hello, I am getting a reflection warning in Java interop and don’t understand why: (import 'java.time.format.DateTimeFormatterBuilder 'java.time.temporal.ChronoField) (set! *warn-on-reflection* true) (let [builder (DateTimeFormatterBuilder.)] (.appendText builder C

Re: Clojure docstring style

2016-05-16 Thread Matching Socks
Cider could be most *helpful* by linking all words that could possibly be linked. Everyone uses clojure.core, after all. Cider could be most *elegant* by not attempting these links at all. Cider could be most *Emacs-like *by letting users override the symbol detector with an Elisp function.

Re: Ghosts in the machine

2016-05-16 Thread Sébastien Bocq
Thanks for sharing! Sébastien Le jeudi 12 mai 2016 02:13:07 UTC+2, Daniel Szmulewicz a écrit : > > Hi all, > > The next version of system 0.3.0 is ready and it is a matter of days > before the official announcement. > > In the meantime, here is a summary of the research that has been carried >

[ANN] debux 0.2.1 is out

2016-05-16 Thread Philos Kim
Debux is a small but useful library for debugging Clojure and ClojureScript. https://github.com/philoskim/debux Change Logs Version 0.2.1 (minor bug fixes): Fixed: An error fixed when using (clog (->> .)) Fixed: An error fixed when using (dbg (let [[a & b] [10 20 30]] ..)) Added: break u