At first I thought the doc was really complicated and hard to understand,
and then I became more familiar with FP and Clojure, and now I think the
doc is perfect, sweet, short and to the point.
What happens with a lot of those higher order functions is that you really
don't understand them unti
On Monday, September 25, 2017 at 11:42:12 AM UTC-5, Phillip Lord wrote:
>
>
>
> Clojure's doc strings, though, contain knowledge that is not
> clear. Consider, this documentation:
>
> Returns a new seq where x is the first element and seq is the rest.
>
> x is the name of a parameter. So is th
As a docstring I don't find this superior. Docstrings (for me) are usually
viewed as quick little pop-up boxes in my editor. The existing clojure
docstring for `apply` gives me the information I need much faster and
with less screen real estate. YMMV.
On Monday, September 25, 2017 at 9:42:12 AM
And if you need specific instructions on filing an issue in JIRA, here they
are:
If you want to be able to create or edit JIRA tickets, create an
account by going to this page:
https://dev.clojure.org/jira/secure/Signup!default.jspa
The link below gives a brief introduction to the process of
Clojure's doc strings, though, contain knowledge that is not
clear. Consider, this documentation:
Returns a new seq where x is the first element and seq is the rest.
x is the name of a parameter. So is the the second occurence of seq, but
not the first. Neither first, nor rest refer to the func
I'm pretty sure you can't use a bare colon - Clojure will attempt to read
it as a keyword and will fail since there's nothing following. :- is just a
normal keyword.
I think you can take the minimalist syntax too far, if there were no
separator at all then you'd have to be counting elements to see
