This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (10)
- # boot (260)
- # cider (44)
- # clojure (226)
- # clojure-berlin (24)
- # clojure-dev (68)
- # clojure-germany (5)
- # clojure-india (14)
- # clojure-italy (3)
- # clojure-japan (21)
- # clojure-poland (34)
- # clojure-russia (20)
- # clojure-spain (2)
- # clojure-uk (8)
- # clojurescript (86)
- # core-async (38)
- # core-typed (70)
- # datomic (41)
- # docs (8)
- # editors (7)
- # euroclojure (6)
- # instaparse (2)
- # jobs (8)
- # ldnclj (47)
- # om (17)
- # other-lisps (1)
- # reactive (1)
- # reading-clojure (8)
- # reagent (13)
- # sneer (1)
- # sneer-br (1)
(run! reduced (range)) returns
0, though the docstring says it “returns nil”. Is this the intended behavior?
@athos not sure if it’s intended behaviour, but looking at the source it will return whatever (proc <last-value-in-coll>) returns. So for example (run! identity ) returns 1, not nil as the doc suggests
Do Clojure and ClojureScript have an official birthday? If not, it seems a serious shortcoming: http://fsharpforfunandprofit.com/posts/happy-fsharp-day/ Should I open a ticket?
@alexmiller: I'm sure it's been discussed and described before, but I haven't found it, so I'll ask again. How come Clojure isn't developed with git pull-requests (and git issues)
It would be better if the patch retained a commit with Jonas's original contribution
There were concerns at one point over whether a pr was a clear point of contribution but that was in the early days of pull requests and may be less of a concern now
concerning the patch with tests, you'd like to have two commits in there? one for Jonas and one for me?
And re github issues, at the point where the decision was made, github issues were really basic. I'm still not sure they are up to the task although they have come a long way.
I think you have quite a workflow going on in Jira, which might be difficult to duplicate in github issues, although I'm not an expert on the subject.
I know lots of people don't like jira but I like it better than github issues for doing real tracking.
If I would like to contribute, what’s a good place to jump in? I’m looking at the jira right now and there are a lot of issues, are there any markers for easy or just documentation fixes?
I think the idea here is really to supplant the almost dead clojure-dev mailing list as a communication media
about other projects, maybe it's better to stick to their official communication channels
Oh, I wasn't talking about getting cider-stuff in here, I was suggesting that the issues in Clojure could be tagged in the same way, so that it'd be easier for people to start contributing.
there is a #C0617A8PQ, but AFAIK user centric. Development discussions are made on Gitter (at least the last time I checked it out)
I like the idea of tagging issues on Jira what we need to do to be able of doing that?
it's just hard to find issues that are a) suitable for newbies b) don't quickly gain patches
the idea of this room is also not to supplant the clojure-dev mailing list but to serve as an additional channel
@alexmiller: supplant was a bit stronger of my part - the mailing list is still a good channel for long-form reasoning, like the last conditional reader stuff
there are many people on the mailing list (like Rich) that are not here and that group is archived and searchable (whereas this one is less so). but sometimes live chat is useful. In the past that's happened on #C03S1KBA2 irc.
another place to look for things useful to work on are Triaged tickets with no patch