I definitely like standard packages, but how will we avoid the problem of this becoming just another threading macro package instead of an actual standard? I also feel like something similar would be useful for anonymous functions, what with curly-fn, rackjure, fancy-app, the cut and cute macros from srfi 26, etc. etc.
If this isn't going to be added to the core (and I don't think it should), then there would need to be some work done on exposure and making sure everyone who wants this functionality knows "look here first and only roll your own if this isn't specific enough". Maybe a Wiki page acting like a swiss army knife of useful single purpose packages that the community has standardized? Also things like Greg Hendershott's threading macro blog post would need to be updated to point to the standardized version, along with other places "non standardized" versions of the functionality have been documented. As for the actual package, I'm a strong proponent of a non-macro version that's just the reverse of compose, mostly because it plays very nicely with anonymous macro functions like fancy-app. I'm a bit biased as that's the one I made in my point-free package however. Macro versions are nice too, but I prefer the flexibility of an actual function for most purposes. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
