This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-07-10
Channels
- # admin-announcements (4)
- # beginners (21)
- # boot (85)
- # cider (31)
- # clojure (45)
- # clojure-australia (1)
- # clojure-berlin (2)
- # clojure-dev (7)
- # clojure-italy (10)
- # clojure-japan (17)
- # clojure-norway (8)
- # clojure-russia (2)
- # clojure-uk (15)
- # clojurebridge (1)
- # clojurescript (115)
- # code-reviews (13)
- # core-async (1)
- # editors (17)
- # euroclojure (5)
- # jobs (1)
- # ldnclj (9)
- # off-topic (5)
- # om (18)
- # re-frame (15)
- # reagent (25)
- # sydney (1)
hello, is cursive working in intellij 15 EAP?
@danielgrosse: doesn’t work for me
any hystrix-clj users here? I would like to mark http://dev.clojure.org/jira/browse/CLJ-1232 screened, but it appears to break hystrix-clj
at first glance it seems to me that hystrix-clj (or any tooling) that wants to manipulate metadata reserved to Clojure should is incorrect if it does not follow Clojure's use of that metadata
grr, English
@stuarthalloway: We're using hystrix-clj, but I think the way we're using it would not be affected. We're not using their defcommand macro.
@mattly: other than pprint?
@danielgrosse: Not yet, hopefully the next build will work there.
@ghadi: What do you mean? There are other bindings for Ring-swagger besides Compojure-api
@juhoteperi: Can you enumerate other approaches?
especially the fnhouse implementation should be quite simple
If I just want to do something side-effecting out-of-process and I don't care about it's return value, is (-> (Thread. do-a-thing) .start)
the most straightforward way?
FWIW I just got burned (again) by unbounded thread creation from future
if you don't know how many times it will be called, always make sure you control the thread pool behind future (or anything like it)
stuarthalloway: allowing to pass options to future (and/or future-call) would be welcomed, same goes for the hardcoded/global threadpools in core.async (I have been trying to push for this for a while).
issue with most votes on c.async -> http://dev.clojure.org/jira/browse/ASYNC#selectedTab=com.atlassian.jira.plugin.system.project%3Apopularissues-panel
In the case of future, it's ok'ish, as we can just create our own "future" function with an additional argument in a couple of lines, in core.async case it's more problematic, there are reference to the hardcoded pools in a few places (go, chan, thread, etc), which makes it hard to "patch" via a library.