Thanks for the answer Herwig! swank-clojure and nrepl(.el) can do pretty amazing things. But in my opinion, at least in the context of Java interop there is still work left to do...
Lastly, as of today, what can clojurescript do that clojure can't? On Saturday, November 24, 2012 11:36:50 PM UTC+1, Herwig Hochleitner wrote: > > I'm not convinced about allowing wildcard imports. Same reason that we > discourage use without :only for. > > About discoverability: I'd take a look at the autocompletion code for > swank-clojure, lein repl, et. al. > Maybe there is a contrib in there? > > About your static/dynamic remark: In static langs there is a clear > distinction between the compile class path and runtime class path. That > way, you can't introduce new names by running with an upgraded library. So > while wildcard imports are still suboptimal, they are not as volatile as in > most dynamic langs. You can protect against that in clojure too by AOT > compiling. > > > That said, package imports with :as clauses, as in your example, wouldn't > even pose this problem. > With (import '[com.package :as pkg]), Symbols using the pkg namespace > alias could be resolved to their classes without walking the classpath. > > That feature might actually be quite nice. I like how one can do that in > clojurescript. > > kind regards > -- 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
