On Tue, Jul 23, 2013 at 12:57 PM, Lee Spector <lspec...@hampshire.edu> wrote: > I'm sure I'm coming from a minority perspective on this, but for the kind of > work I do it's often more important to be able to quickly sketch out and test > ideas, without any ceremony about which functions come from where, than it is > to ensure safety in a "production" environment which is really just me > running it right now. > > In fact I'd sometimes like to go the other way and use everything in a whole > directory subtree, or even to get rid of "using" altogether and have the > runtime system find the function wherever it can (within reason :-) and let > me know if it can't or if there's a conflict. > > I do understand that there are a great many programming contexts in which it > would be foolish and dangerous to manage references so loosely and implicitly > and dynamically. In fact it's a bad idea in some of my work too, so I'm > slightly more disciplined than this some of the time. > > But my point is just that different users will have different priorities, and > from where I sit, at least, it'd be nice to keep :use.
Well, you can always use (require '[some.ns :refer :all]) instead of (use 'some.ns) but I recognize the former is a lot more typing. Certainly in the REPL, working in the user ns, I can see a good argument for (use 'some.ns) while you're evolving a solution, but I think :use in the ns macro should be deprecated (i.e., :use should at some point go away but perhaps the use function should stay for REPL-based exploration?). Tightening up the ns macro so it issues warning for undocumented constructs would also be a good idea: (ns some.ns (require [foo.bar :as f])) ;; supported and works, but really should be :require instead! -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- -- 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.
