Re: Conflicting definition for IPersistentVector

2010-04-27 Thread Dan
On Apr 26, 4:54 pm, Rich Hickey wrote: > On Apr 13, 2010, at 9:37 AM, Dan wrote: > > > I'm a Java developer; I work on a project that has adopted Clojure's > > data structures as a convenient implementation of immutable sets, > > maps, etc.  In attempting to add type parameters to the Clojure > >

Re: Conflicting definition for IPersistentVector

2010-04-26 Thread Rich Hickey
On Apr 13, 2010, at 9:37 AM, Dan wrote: I'm a Java developer; I work on a project that has adopted Clojure's data structures as a convenient implementation of immutable sets, maps, etc. In attempting to add type parameters to the Clojure interfaces, I noticed a conflict in the definition of IP

Re: Conflicting definition for IPersistentVector

2010-04-26 Thread Dan
Bumping. Let me emphasize this paragraph, which is really the crux of the problem: > Put another way, the problem is that if I have an Associative which I > know maps integers to strings, and I invoke seq(), I don't know what > kind of values I'm going to get. Is this expected behavior or a bug?

Conflicting definition for IPersistentVector

2010-04-14 Thread Dan
I'm a Java developer; I work on a project that has adopted Clojure's data structures as a convenient implementation of immutable sets, maps, etc. In attempting to add type parameters to the Clojure interfaces, I noticed a conflict in the definition of IPersistentVector. I assume the problem exist