Thanks for mentioning it, Rob. (I have looked at Prismatic Graph before. Putting arguments in a graph (at macro time) is a powerful idea; plumbing uses this to offer a declarative way to offer various evaluation strategies. It is nice to show off Clojure macros! In this case, it makes Clojure feel more like Haskell or other lazily-evaluated languages.)
When it comes to the use case I showed above, I don't think Graph would address the core problem of memoization. Graph has a memoization function, but it does not work with a graph to track cross-function arguments, like I would need in my example above. Perhaps it could be extended to do so. Perhaps it would be easier to roll my own. I'm still interested in having a discussion about all of the questions I asked: - Have others faced [the many arguments vs one composed thing, such as a map or object] tradeoff? - How do you think about it? - How do you strike a balance, if there is one? - More pointedly, is there a way to get the best of both worlds (e.g. the "composed" argument style AND memoization)? -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
