Hi, Am 31.01.2009 um 15:55 schrieb André Thieme:
On 31 Jan., 02:47, Jason Wolfe <jawo...@berkeley.edu> wrote:I think this behavior is as-intended, although I agree that it is confusing.I am worried that you could be right. That’s why I suggested to modify the doc string of lazy-cat. In my opinion the real step that needs to be done is to go away from making nil the empty sequence.
I'm not sure, that nil itself is the problem. I think, the translation to Java null is the problem. If nil was a normal Object, which can be asked whether it's nil or not, lazy-cat could return an object, which determines whether it's nil or not only when asked for it... ISeq would then simply get another method isNil. But I have no clue about language design. So this might have other negative implications, which I almost surely haven't thought through. Sincerely Meikel
smime.p7s
Description: S/MIME cryptographic signature
