Fork me on GitHub
#clojure
<
2015-07-10
>
danielgrosse12:07:35

hello, is cursive working in intellij 15 EAP?

caskolkm13:07:38

I don’t know, i get incompatibility messages

dnolen14:07:13

@danielgrosse: doesn’t work for me

stuarthalloway15:07:26

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

stuarthalloway15:07:34

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

hlship16:07:08

@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.

jthomson16:07:37

we're using it in production, but similarly not using defcommand

pbostrom16:07:03

we use defcommand

mattly17:07:01

is there a version of prn-str that will pretty-print complex, nested edn structures?

stuarthalloway17:07:15

@mattly: other than pprint?

mattly17:07:06

ah, pprint doesn’t work in cljs, where I’m doing this – I’ll ask in the cljs channel

ghadi17:07:37

Who does Swagger integration without Compojure-api?

bhagany17:07:24

@mattly pprint was recently ported to cljs

mattly17:07:01

another reason to upgrade

cfleming17:07:51

@danielgrosse: Not yet, hopefully the next build will work there.

juhoteperi19:07:04

@ghadi: What do you mean? There are other bindings for Ring-swagger besides Compojure-api

ghadi19:07:28

@juhoteperi: Can you enumerate other approaches?

juhoteperi19:07:01

especially the fnhouse implementation should be quite simple

ghadi19:07:43

oh, thanks.

voxdolo19:07:41

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?

voxdolo20:07:12

don't care about the return value though

ghadi20:07:19

then just ignore it

voxdolo20:07:21

just never deref and ignore that part of it?

voxdolo20:07:23

hah, okay simple_smile

voxdolo20:07:41

cheers ghadi simple_smile

ghadi20:07:05

(future takes care of dynamic thread bindings for you...)

ghadi20:07:24

(in case you have the misfortune of a lib that uses those extensively)

stuarthalloway20:07:57

FWIW I just got burned (again) by unbounded thread creation from future

stuarthalloway20:07:21

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)

mpenet21:07:54

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).

mpenet21:07:02

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.

ghadi22:07:48

mpenet: hey Max

ghadi22:07:15

I hope we can take care of the async thread issues soon

ghadi22:07:41

^ That's the design doc for golang's scheduler. Worth a read IMHO

magnars22:07:18

'ello folks simple_smile

mpenet22:07:53

ghadi: intresting, it's a bit late here (1am), I ll read this more carefully tomorrow.