Do you really need core.async for this?
Seems like you can just normally call the service to get the token once at
the beginning and then just go in a normal loop of calling for the next
message -> handling message -> repeat.
I'm not sure there's any reason to use core.async in ClojureScript
Wow, awesome!
On Monday, 12 November 2018 07:46:14 UTC-8, Chris Nuernberger wrote:
>
> Clojurians, we are happy to put forth our work bringing the TVM compiler
> and infrastructure to clojure. It has backends for ARM, Intel, OpenCV,
> Cuda, OpenGL, Vulkan, ROCm, and more.
>
> This system is
This is somewhat of a retrospective -- so please bear with me. I've had the
privilege of working on a clojure project for a couple of years now, and have
accumulated some 15-20k lines of clojure code. I'm taking a little time to
look back over what has worked for me and what hasn't in terms
I have run versions 0.2.6 and 0.3.3 of the Eastwood Clojure lint tool on 84
projects in its "crucible" set of projects that we use for testing
Eastwood. You can find the list at [2].
I tried comparing the output for these pairs of version combinations of
(Eastwood version, Clojure version, JDK
I've been happy using a monorepo with boot, and a build.boot with many building
blocks that can be mixed and matched for many deployables (uberjars in my case).
In my build.boot I define my internal blocks, but also defs for external deps
like eg postgres and grpc. That way I have one place for
