On Apr 6, 4:46 pm, Jarkko Oranen <chous...@gmail.com> wrote: > problem is that they also make some very common functional patterns > cumbersome: most notably function application (ie. apply), > composition, and higher-order functions.
I don't think it should be either-or (and positional would be needed anyway to call out to Java & friends). So your functional patterns could still be done positionally, since the first-class function arguments f & g are not named anyway: (let [f ..., g ..., x ...] (apply f g x) (comp f g)) The arg-lists in the defn would distinguish ;; positional-keyword calls needed ;; function name is a composite ;; one "defn" could create more than one function name (defn schedule [project: p before: b after: a priority: i] ...) from ;; existing defn & calling code could even be unchanged ;; no keywords (defn apply (f args* argseq) ...) -- 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 To unsubscribe, reply using "remove me" as the subject.
