-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Provide way to use tuples instead of list for "all" #36
Comments
Thanks for the suggestion :) This should be easy to implement on native as well. I can do it later today/tomorrow :) I'd probably create |
Awesome! Yeah, I think replicating the |
Okay, Sorry about the delay, I needed to take a break from public work for a while :/ |
@aantron that's awesome, thanks so much! And no worries about the delay - hope all is well. Thanks again for this great lib! |
Great :) Are you depending on Repromise from GitHub? Would you prefer a speedy release of these functions to NPM? |
Yeah, I'm using the npm package, not GH, but I'm also not stuck waiting on this. So, no rush to ship a new release if you want to wait a bit. |
Ok, thanks. I'll see if I get around to doing anything else soon-ish, then do a release. |
Hi! I just bumped up another use for this - would you mind cutting a release with this code when you have a chance? |
Hey there! Thanks so much for this library - I'm really enjoying using it in my project over the standard
Js.Promise.t
!One API that
Js.Promise
provides that I do miss, however, is the ability to resolve a set of promises in parallel that don't all have the same type via a tuple.From the JS side, I think the implementation would be pretty easy:
But, I'm not as familiar with writing native Reason code, so I've got no idea if it'd be that straightforward there... and if it isn't, I presume the idea would be to keep the API the same for native and JS, right?
The text was updated successfully, but these errors were encountered: