What blog posts did you find useful?
On Tuesday, May 26, 2015 at 10:01:29 PM UTC-4, andy.c...@fundingcircle.com
wrote:
This page on Jira says that dynamic binding should be documented as The
Clojure Way to do error handling. Was this ever done? I managed to find a
few blog posts
I like it when someone says 'do not do this' without some supporting
cost/benefit rationale.
My next question is why not ?
I'll add my own salt here:
- Daemonizing does not alter business logic, it can be kept separate using more
than one entry point
- Supervisory functions are not as
I see what you mean, this is nice [?]
On Thu, May 28, 2015 at 11:25 PM, Herwig Hochleitner hhochleit...@gmail.com
wrote:
2015-05-28 19:42 GMT+02:00 Mohit Thatte mohit.tha...@gmail.com:
The interesting question here is what constitutes useful information!
(let [pred #(exists? .foo)]
I wonder whether it's been dropped because of threads. (If I understand
correctly, you have to remember to tell the thread to inherit dynamic
bindings. Which may be difficult if you have a framework creating threads
as an implementation detail...)
On Wednesday, May 27, 2015 at 4:01:29 AM
Stuart, about the JSVC, I am curious if you have an opinion about the
argument made in the comments of this blog post:
Great post, but in reality you should never write app that daemonize them
self. Always use supervisors that your system provides.
Thank you all. I especially like the use of reduce-kv and the 2 fnils. I
looked at reduce-kv, but I was too stupid to figure out how to apply it
here.
On Tuesday, May 26, 2015 at 12:27:16 PM UTC-4, Francis Avila wrote:
Your two functions can be written more succinctly (and with fewer
I think I might have found a bug that affects multimethod dispatch
when using AOT. I've created an example repository:
https://github.com/sfnelson/clj-mm-dispatch
To me it seems similar to CLJ-979, my hypothesis is that defmethods
are using the wrong classloader to get class references. Is anyone
Take a look at my project.clj file.
https://github.com/Skinney/oslo-programmene/blob/development/project.clj
fredag 29. mai 2015 11.17.25 UTC+2 skrev Colin Yates følgende:
In the vein of there are no stupid questions :), how does one structure
a combined clj and cljs project that uses reader
Thanks Robin, that was helpful. I notice that you are using garden 1.2.6 - that
throws a CNF for garden.core and the garden page recommends not using it - does
it work for you?
On 29 May 2015, at 10:49, Robin Heggelund Hansen skinney...@gmail.com wrote:
Take a look at my project.clj file.
No, it doesn't. I update with `lein ancient update :all` and committed
without checking if it worked. It's fixed locally :)
fredag 29. mai 2015 12.01.32 UTC+2 skrev Colin Yates følgende:
Thanks Robin, that was helpful. I notice that you are using garden 1.2.6 -
that throws a CNF for
In the vein of there are no stupid questions :), how does one structure a
combined clj and cljs project that uses reader conditionals? At the moment
I am using cljx and have:
- src/clj for clojure files
- src/cljs for clojurescript files
- src/cljx for cljx
- target/cljx/clj for clojure
Hey, Thanks Herwig Mohit.
So, I have one more solution.
Here is the original wait-until function-
(defn wait-until
([pred] (wait/wait-until *driver* (fn [_] pred))) ([pred timeout] (wait/
wait-until *driver* (fn [_] pred) timeout)) ([pred timeout interval] (wait/
wait-until *driver* (fn
I just tried to upgrade a clj/cljs webapp I wrote. I got an error but it
was just a transitive dependency issue with instaparse
https://github.com/Engelberg/instaparse/issues/90.
Everything works great now that I'm using up-to-date dependencies!
On Thursday, May 21, 2015 at 11:31:16 AM UTC-5,
Hey BG,
Yes, having metadata is really a straight forward way but this is kind
of extra work in every wait-until call which I was trying to avoid. Going
with metadata option will not just cause extra work for wait-until in
future code but even I need to add it at all the places in wherever
Shalaka,
This is a really interesting conversation :-) However, I'd insist that you
ditch eval or any sort of complicated affair and adopt the metadata
approach as I had suggested that day :-P
~BG
On Fri, May 29, 2015 at 4:20 PM, Shalaka Patil shal...@helpshift.com
wrote:
Hey, Thanks Herwig
http://blog.paralleluniverse.co/2015/05/29/quasar-pulsar-0-7-0/
Pulsar 0.7.0 https://github.com/puniverse/quasar/releases/tag/v0.7.0
introduces *automatic instrumentation for Clojure code* so you don’t need
those suspendable!, defsfn and sfn (enabling this feature carries a small
performance
May be wrap it up in a `wait-until-with-meta` macro as Herwig suggested?
Then you can search and replace the invocations. ~BG
On Fri, May 29, 2015 at 9:30 PM, Shalaka Patil shal...@helpshift.com
wrote:
Hey BG,
Yes, having metadata is really a straight forward way but this is kind
of extra
When porting a library to reader conditionals, I found that I only needed
one source directory for all my cljc and .clj files. Cljsbuild just picks
up the ones it needs and leaves the .clj ones.
So in some cases it may not be necessary to have a clj/, cljs/, and cljc/
folder, although in
18 matches
Mail list logo
