Okay, I'm not sure what the correct thing do for the entire library is, but I think I've got a convincing argument for some functions.
The following functions share a name with core functions butlast contains? drop get partition repeat reverse take These functions should follow their corresponding signature in core. I found it difficult to remember "which way" the signature was supposed to go, even when writing one post on this list. I suspect that newcomers would find this difficult as well. I would make an exception for the following method: replace I don't think the signature in core makes sense, because the core fn takes a map. When I use str-replace, I would like certain guarantees about the order operations are applied in, and I don't think this is possible when the data is passed in as a map. Just another thing to think about. Sean On Aug 20, 11:26 am, Stuart Sierra <the.stuart.sie...@gmail.com> wrote: > Seems like opinion is pretty evenly divided here. I'll leave the > library as-is for now, give it some time to see how things play out. > > In the mean time, as a compromise, I've added str-utils2/partial, > which is like clojure.core/partial for functions that take their > primary argument first. > > (str2/partial str2/take 2) > ;;=> (fn [s] (str2/take s 2)) > > Now you can compose these using comp, map, whatever. > > -SS --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
