Paul Mooser <taron...@gmail.com> writes: Hi Paul,
> Looking at the stack trace, I suspect this is the old problem of > layering too many filters on top of the same seq. If I understand the > issue correctly, when you have enough layers of filter on top of a > seq, when you finally try to access elements, as it evaluates each > layer, it is going to be making a call for each layer of filter. With > enough layers, you'll blow your stack. Do you have a link to the issue? I've tried searching for "filter" or "layer" at dev.clojure.org, but I can't find anything... > I've seen people solve these issues by forcing the intermediate seqs, > but that doesn't work well for a lazy situation such as this. Indeed, putting a doall around the filter and remove seems to prevent the stack overflow. Bye, Tassilo -- 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 Note that posts from new members are moderated - please be patient with your first post. 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
