Hi,
I fear that I have to excuse me for triggering a debate about principles of
behavior patterns on this list. Of course, I tried to answer my question
myself using Google. Perhaps I made a mistake on the selection of the right
search pattern so I didn't find satisfactory results. The
My apologies (sincerely). Won't use that again.
--
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
Are you tired of writing the same clj-http/cljs-https boilerplate? Looking
for an easy way to express an endpoint or a service API? Then remote is
the library for you!
Github: https://github.com/outpace/remote
Leiningen: [com.outpace/remote 0.3.1]
This library has been closed source up until
I took a swing at this using prismatic schema:
(ns schema-test.core
(:require [schema.core :as s]
[schema.utils :as utils]
[schema.coerce :as coerce])
(:import schema.core.NamedSchema))
(def Alternate (s/named [s/Keyword] alternate))
(def Path (s/named [(s/either
Sorry about the double threads - I messed up and thought the original post
didn't go through.
Looking further into this it seems in Java generics are largely a compile
time thing. The generic type information is wiped out from the type on
compile. So how does Java know which overload to call when
I want to fully understand what is going on before doing anything.
Interestingly if I convert the Java code below to Scala it fails to compile
with the same error :
def Onk(str: util.ArrayList[String]): String = {
println(String)
erk
}
def Onk(it: util.ArrayList[Integer]): Integer = {
Have you considered writing a wrapper method in Scala and calling that?
Thanks,
Ambrose
On Fri, Jun 26, 2015 at 7:24 PM, Stephen Wakely fungus.humun...@gmail.com
wrote:
Sorry about the double threads - I messed up and thought the original post
didn't go through.
Looking further into this it
