> I think I read somewhere that max-key applies f more times than is > necessary, so should not be pass any f that takes significant time to > compute.
Yes, max-key calls f more times than necessary. http://code.google.com/p/clojure/issues/detail?id=95 We ran into this problem yesterday on a tic-tac-toe project, in which f was a function that determines who is winning for a given board position. Tests that previously ran in under a minute now took over 10 minutes (that's roughly how long I waited before stopping it). We fixed our program by replacing max-key with the alternative implementation from the above link. http://github.com/ericlavigne/tic-tac-toe/commit/0d172c45c9d462620af8b819db53e19ab6382bf6 -- 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
