Re: Bug: LazySeq.equiv()

2009-02-17 Thread Rich Hickey
On Feb 17, 8:48 pm, Chouser wrote: > On Tue, Feb 17, 2009 at 8:37 PM, Chouser wrote: > > Empty lazy seqs do not always compare as equal: > > > user=> (= (map inc nil) ()) > > false > > The problem appears to be when the first seq being compared is empty > but not identical to the second collec

Re: Bug: LazySeq.equiv()

2009-02-17 Thread Chouser
On Tue, Feb 17, 2009 at 8:37 PM, Chouser wrote: > Empty lazy seqs do not always compare as equal: > > user=> (= (map inc nil) ()) > false The problem appears to be when the first seq being compared is empty but not identical to the second collection. The attached patch fixes this and is I think

Bug: LazySeq.equiv()

2009-02-17 Thread Chouser
Empty lazy seqs do not always compare as equal: user=> (= (map inc nil) ()) false The problem is in IPersistentCollection equiv: user=> (.equiv (map inc nil) ()) false --Chouser --~--~-~--~~~---~--~~ You received this message because you are subscribed to the G