Is the future returning a lazy seq? You might need to walk the seq with
doseq / dorun etc.
On Mon, Feb 15, 2016, 6:02 AM Gary Verhaegen
wrote:
> `future` starts a function in a separate thread, which comes out of a
> thread pool. It may not be that easy to check if a future has run at
> all if y
`future` starts a function in a separate thread, which comes out of a
thread pool. It may not be that easy to check if a future has run at
all if you don't hold onto the future object and wait for it.
How did you check if they run? It's possible, for example, that they
are sending their print's to
I have a function which calls a number of functions in sequence. Few of
them are normal functions and some of them use clojure's 'future' method.
When I run this function, All the normal fuctions run but the functions
which use 'future' don't run at all. But if I run the functions which use
'fu
