11–20 of 46 posts
> and Clojure’s syntax is pretty limited Erm, what? I am confused by the use of the word 'limited' in this context.
I confirm: the syntax is limited. There are only a few keywords and langage constructs. The power is in the number of functions made available, or the ones you create for yourself.
Earlier quoted context omitted.
I confirm: the syntax is limited. There are only a few keywords and langage constructs. The power is in the number of functions made available, or the ones you create for yourself.
Doesn't Clojure have reader macros? The whole point of lisps is that you can extend them.
The equivalent of `flatMap` is not `flatten`. Semantically `flatMap` is equivalent to `(comp flatten map)` – hence the name! – but Clojure does offer it as a single function named `mapcat` (”map and catenate”).
With the caveat that `flatten` is recursive and can handle a mix of collections and non-collections, while `mapcat` is non-recursive and every value returned by the mapcatted function must be a collection or nil.
(Identity returns its argument.)
(flatten [1 [2 3] [[4 5 6]]])
> [1 2 3 4 5 6]
(mapcat identity [1 [2 3] [[4 5 6]]])
> IllegalArgumentException Don't know how to create ISeq from: java.lang.Long
(mapcat identity [[1] [2 3] [[4 5 6]]])
> (1 2 3 [4 5 6])
(flatten [nil [1 2 3]])
> (nil 1 2 3)
(mapcat identity [nil [1 2 3]])
> (1 2 3)The equivalent of `flatMap` is not `flatten`. Semantically `flatMap` is equivalent to `(comp flatten map)` – hence the name! – but Clojure does offer it as a single function named `mapcat` (”map and catenate”).
Earlier quoted context omitted.
I confirm: the syntax is limited. There are only a few keywords and langage constructs. The power is in the number of functions made available, or the ones you create for yourself.
Doesn't Clojure have reader macros? The whole point of lisps is that you can extend them.
Earlier quoted context omitted.
Doesn't Clojure have reader macros? The whole point of lisps is that you can extend them.
Actually, Clojure does not have reader macros, because it was thought to be the biggest cause of the lisp curse.
> and Clojure’s syntax is pretty limited Erm, what? I am confused by the use of the word 'limited' in this context.
> and Clojure’s syntax is pretty limited Erm, what? I am confused by the use of the word 'limited' in this context.
No pun intended, by "value" I mean "things that are worthwhile". Clojure is totally into "values". :-D
Also, this bit: (->> justice-league (map #(:vehicles %)) (filter #(not (nil? %))) (flatten)) can be simplified to just `(mapcat :vehicles justice-league)`
- Keywords (i.e. `:vehicles`) can be used as getter functions, as covered in the OP.
- mapcat (like most collection functions in clojure) treats `nil` as an empty sequence
Earlier quoted context omitted.
Actually, Clojure does not have reader macros, because it was thought to be the biggest cause of the lisp curse.
Nit: Clojure does not have user-defined reader macros. There are quite a few built-in reader macros, including #? added for reader conditionals.