Re: Implementing a generic parameterized Java interface so that it satisfies (instance? ParameterizedType)

The JVM does retain some generic information (see for example Neil Gafter's Super Type Tokens), in particular Type instances can retain generic info which is what the linked code is using. It might be possible to recreate this in pure Clojure but IMO it's likely to be more difficult than it's worth

Do you use any Clojars data feeds?

Clojars provides a few static data feeds[1]: - a list of poms in the repo (all-poms.txt.gz) - a list of all releases in the repo (all-jars.clj.gz) - an expanded list of releases, including more metadata from the poms (feed.clj.gz) We're evaluating our bandwidth usage in anticipation of moving the

Re: Implementing a generic parameterized Java interface so that it satisfies (instance? ParameterizedType)

I'd dig into it a bit more, since the JVM doesn't support generics either. So if there's an api looking for some marker interfaces, it might be possible to implement those interfaces as well. There's probably a way to do this in pure Clojure. On Thu, Aug 4, 2016 at 4:55 PM, Colin Fleming wrote:

Re: Implementing a generic parameterized Java interface so that it satisfies (instance? ParameterizedType)

Hi Jakub, Yes, that is correct - Clojure interop only deals with raw classes, it has no concept of generics. Java is the way to go here. Cheers, Colin On 5 August 2016 at 09:28, Jakub Holý wrote: > I need to implement the interface javax.websocket. > MessageHandler.Whole - the type parameter i

Implementing a generic parameterized Java interface so that it satisfies (instance? ParameterizedType)

I need to implement the interface javax.websocket.MessageHandler.Whole - the type parameter is important since the Java code uses reflection to check

Re: Is this behavior of clojure.core/pr a bug?

2016-08-04 13:56 GMT+02:00 Timothy Baldridge : > The problem is that many do not understand that Clojure data is a superset > of EDN. The two were never meant to be completely compatible. There are > many things, especially when dealing with keywords and symbols, where its > possible to have data

Re: Is this behavior of clojure.core/pr a bug?

The problem is that many do not understand that Clojure data is a superset of EDN. The two were never meant to be completely compatible. There are many things, especially when dealing with keywords and symbols, where its possible to have data that doesn't properly round-trip. An added problem when

Re: Is this behavior of clojure.core/pr a bug?

2016-08-04 1:41 GMT+02:00 Timothy Baldridge : > I highly suggest using transit. It's much faster and formally specified. > https://github.com/cognitect/transit-format > > It's issues like this that caused the creation of transit in the first > place. > I thought transit was created to take advan

Re: Is this behavior of clojure.core/pr a bug?

> Can anyone think of a good reason why pr should *not* throw an exception on > (pr (keyword “foo bar")) > since there’s no way of expressing that keyword as valid EDN? This would break backwards compatibility, something Clojure rarely does. On Thu, Aug 4, 2016 at 1:16 PM Blake Miller wrote: >