This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (11)
- # boot (121)
- # bristol-clojurians (3)
- # cider (5)
- # cljs-dev (45)
- # clojure (122)
- # clojure-conj (3)
- # clojure-germany (1)
- # clojure-japan (9)
- # clojure-russia (48)
- # clojurescript (129)
- # community-development (2)
- # cursive (17)
- # datomic (11)
- # editors-rus (3)
- # events (2)
- # funcool (32)
- # ldnclj (22)
- # om (110)
- # onyx (15)
- # re-frame (2)
Hi @niwinz, I was looking for a portable promises abstraction and found your promesa and promissum libraries.
Was wondering if you’d considered bridging the gap and provide some kind of portable interface?
I mean that the differences between the two promises are just becuase of platform differences
and the promise constructor differes a little bit because in cljs/js an error can be anything so is no way to distinguish between values, because of this the cljs constructor receives 2 callbacks and the clj one...
Maybe is possible package them in one unique library, but at this moment I don't know if that a proper way...
yeah I wonder if you could set up your maven deps so that the cljs part wouldn’t require jdk8
Hmm, I will think about, maybe you are right and package them together seems a good idea
Cool, could you elaborate a little bit on the difference in error handling that requires different promise constructors? I’m not sure I understand why this is necessary
because it there isnt' any way to distinguish if an value is an error or an valid value
In any case I'm pretty convinced now that differences can be handled properly in one unique package
Yeah I’m still not sure why you wouldn’t be able to catch any object getting thrown in a promise’s fn ctor
Ok cool, I’m sure this will be really helpful, I’ve been working on a protable ring-cps http client and don’t want to add promises to the middleware stack, but they would be really useful as adapters 😉