You can just use seq function to do this: user=> (seq “aaa”) (\a \a \a) for numbers you can use “dumb” solution, something like: user=> (map (fn [^Character c] (Character/digit c 10)) (str 12345)) (1 2 3 4 5) P.S. strings in clojure are ‘seq’able, so you can use them as source for any sequence … Read more
You can generate Maven’s POM out of Leiningen’s project definition and then use Maven’s dependency:tree plugin with a verbose option, like this: $ lein pom $ mvn dependency:tree -Dverbose=true This will list dependencies omitted for various reasons, e.g.: | +- ring:ring-core:jar:1.4.0:compile | | +- (org.clojure:clojure:jar:1.5.1:compile – omitted for conflict with 1.7.0) | | +- (org.clojure:tools.reader:jar:0.9.1:compile … Read more
General intro: Symbols in any Lisp are used as identifiers. If you’re going to refer to the value of a variable, say, you need to have a way of naming it; that’s what symbols are for. Remember that all Lisp code gets translated at read time to Lisp data structures; identifiers must also be represented … Read more
just use or: (or input-argument “default”)
Replying to your numbered points, it is idiomatic in Clojure to interoperate directly with Java libraries, so getting the full Java stacktrace can be helpful if you are calling into Java objects in some unexpected or unsupported way. Sounds like a good idea; I’ve often at least wished for a settable option which would allow … Read more
You should namespace-qualify your keywords if any code is ever going to have a chance to interact with your keywords outside of the context of your namespace. The main example I can think of is two namespaces putting keys and values into a hash-map in a third namespace, where the keys are keywords (as they … Read more
No, it’s intentionally not possible. There was a conversation on the ClojureScript mailing list recently related to :refer :all and it looks like it will never be supported. To quote David Nolen from that thread: It’s just bad style and as far I know the only reason it hasn’t changed in Clojure is because the … Read more
On the top of my head: good IDE support (with refactoring) stable enough specifications clear policy about backward compatibility (in term of sources, binaries and behavior) frameworks and tools around the language (like code static analysis, code coverage, …) Scala, for instance, is still evolving and moving “too fast” to be “largely” used even though … Read more
You’re looking for Integer/parseInt. user=> (map #(Integer/parseInt %) [“1” “2” “3” “4”]) (1 2 3 4) You have to wrap Integer/parseInt in an anonymous function because Java methods aren’t functions. read-string would also work in this case: user=> (map read-string [“1” “2” “3” “4”]) (1 2 3 4) read-string reads any object from a string, … Read more
REPL = read eval print loop. Step through the read-eval process. READ: Clojure sees the string “(`a)”, parses it and ends up with a data structure. At read time, reader macros are expanded and not much else happens. In this case, the reader expands the backquote and ends up with this: user> (read-string “(`a)”) ((quote … Read more