Hi Daniel,

Allow me to recommend a couple of libraries:
- promissum (https://github.com/funcool/promissum) is a composable
promise/future library for Clojure (built on top of jdk8 completable
futures)
- promesa (https://github.com/funcool/promesa) is a wrapper around the
Bluebird JS promise library

They both integrate nicely with cats (https://github.com/funcool/cats),
which lets you write asynchronous code like it was synchronous with the
`mlet` macro that desugars into monadic bind. We also have an `alet`
macro that uses applicative bind and thus maximizes concurrency, take a
look at the docs for more details.

cats is also integrated with core.async and manifold libraries, so you
can use the same code regardless of what concrete type you use for
conveying asynchronous values.

Regards,

Al

On Tue, Oct 27, 2015, at 00:48, Chris Murphy wrote:
> 
> Here are some discussions around the issue:
> 
> http://stackoverflow.com/questions/31832599/future-failure-in-clojure
> 
>   ~ Chris
> 
> On 27/10/2015 9:46 AM, Daniel Hinojosa wrote:
> > I am looking for a functional, non-blocking way to process the return 
> > of a future. In the Scala world, you can use map, flatMap, and foreach 
> > to process the return values of a future asynchronously.  In Clojure, 
> > dereferencing blocks, so that makes it kind of rough since we have to 
> > set up our constructs.  If anyone can steer me on the "Functional 
> > Clojure way" to process futures and promises that would be greatly 
> > appreciated. ;)
> > -- 
> > You received this message because you are subscribed to the Google
> > Groups "Clojure" group.
> > To post to this group, send email to clojure@googlegroups.com
> > Note that posts from new members are moderated - please be patient 
> > with your first post.
> > To unsubscribe from this group, send email to
> > clojure+unsubscr...@googlegroups.com
> > For more options, visit this group at
> > http://groups.google.com/group/clojure?hl=en
> > ---
> > You received this message because you are subscribed to the Google 
> > Groups "Clojure" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> > an email to clojure+unsubscr...@googlegroups.com 
> > <mailto:clojure+unsubscr...@googlegroups.com>.
> > For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> --- 
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
  Alejandro Gómez
  alejan...@dialelo.com

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to