Or maybe people are confused because the :private metadata *complects* two separate concerns : *API commitment* and *visibility*. If there was a way to programmatically make the distinction between implementation and API without impacting visibility, it would be tremendously valuable for tooling and I would definitely use it.
On Saturday, March 3, 2018 at 6:02:00 PM UTC+1, Alex Miller wrote: > > > ^:private is the stale and sleazy co-conspirator of another blunt > instrument, the whole-ns :use. > > It’s also useful for anything that uses the var meta to show you only > public vars in an ns, such as dir, ns-publics, etc. those are all useful > and would affect your repl experience even if you never :use or :refer > :all. > > I find people have different relationships with :private depending on what > kind of work they do. It’s very useful in in libs for delineating public > apis, much less important in an app context. -- 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.
