On Mar 23, 2009, at 14:26, Mark Volkmann wrote: >> That leaves the question whether there is still any need for the >> clojure.lang.ISeq implementation. At the moment it is used for lists, >> but that is not particularly consistent. I guess I will remove it. > > Maybe you should keep it to support custom kinds of sequences that > implement ISeq, but not one of the other interfaces like > IPersistentList.
Among the built-in data types, none does as far as I know. Those who implement new data types with ISeq should also provide an implementation for fmap, in order to make sure that the return type is right and that the semantics are right as well. For example, maps implement ISeq, but a default implementation for ISeq would not be correct for maps. Konrad. --~--~---------~--~----~------------~-------~--~----~ 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 To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
