Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

question on future(...) contruct use #30

Open
dalegaspi opened this issue Oct 16, 2019 · 1 comment
Open

question on future(...) contruct use #30

dalegaspi opened this issue Oct 16, 2019 · 1 comment

Comments

@dalegaspi
Copy link

is there an equivalent construct here that allows something like this:

(require '[diehard.core :as dh])
(dh/with-retry {:retry-on TimeoutException
                :max-retries 3}
  (fetch-data-from-the-moon-future))

where fetch-data-from-the-moon-future is a future(...) and of course the function will return another future?

...i mean it doesn't have to be a future, it can be a thread or anything else as long as async construct equivalents are available.

@sunng87
Copy link
Owner

sunng87 commented Oct 19, 2019

At the moment it is not possible. Can you put the synchronise block into a future, like

(defn fetch-data-from-the-moon-future []
  (future
    (dh/with-retry {:retry-on TimeoutException
                           :max-retries 3}
      (fetch-data-from-the-moon))))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants