Yea, I have a single namespace with project-specific common utilities which I refer to as u/some-util-function. For me, it's a bit scary to have implicit symbols in scope. A typo can make a local binding refer to something that might not exist in production, or at least not what's intended. Conversely, I don't want extra code in my project that has nothing to do with the project. Seems useful to enforce a separation of the artifact from the tools that made it, more-so for a lib that other things depend on than a production app.
The 'user' namespace can cover the use-case of convenience functions? Or, you can add those symbols dynamically at run-time when you need to with something like: https://github.com/flatland/useful/blob/develop/src/flatland/useful/ns.clj#L26 or some aggregated (require ..) calls. On Tue, Jul 23, 2013 at 2:46 PM, Steven Degutis <sbdegu...@gmail.com> wrote: > For much the same reason, I've been using :require with :as and a > one-or-two-letter alias, so I can do x/whatever. Generally works well. > > > On Tue, Jul 23, 2013 at 1:38 PM, Lee Spector <lspec...@hampshire.edu>wrote: > >> >> On Jul 23, 2013, at 2:27 PM, Gary Trakhman wrote: >> >> > We should scour clojuresphere for uses of 'use' and automatically post >> github issues to the projects of interest, and redefine the ns macro to >> issue a warning with use. >> > >> > Does anyone actually like 'use'? >> > >> > Require is always more evident. >> >> I like it and I use it regularly, mainly, I guess, when all of the >> namespaces are my own and I know there are no conflicts. I split things >> into namespaces to keep the project organized, etc., but I don't want to >> have to qualify everything everywhere. >> >> -Lee >> >> -- >> -- >> 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/groups/opt_out. >> >> >> > -- > -- > 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/groups/opt_out. > > > -- -- 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/groups/opt_out.