-
Notifications
You must be signed in to change notification settings - Fork 17
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
Promise.map(), Promise.filter(), etc. return native Promises instead of Bluebird #72
Comments
k |
What you did won't do. As long as an |
Hey there :) This project looks very promising - nice work! I have a couple of questions, if you may:
Thanks! |
No to both. Sadly, as it currently stands, |
I see. It would have been really nice if there was a way to monkeypatch native promises to support these kinds of things that will probably never make it to ECMAScript... |
There was a proposal that allowed this - it was rejected (compositional functions) There was another proposal that allowed this (cancellable promise) which was also rejected. Sorry - the good people of th TC don't like these proposals very much - and the sad truth is that there is politics involved. On the other hand, you can manually use tokens |
I don't care very much for tokens - I started using them when I thought the proposal will be accepted but once it was dropped I decided to go back to bluebird-style cancel which is a much better approach in my eyes. The question is: is it possible that node will ever provide its own hooks for extending promises, regardless of the ECMAScript standard? It seems like a pretty simple |
@itsysabato - we can discuss this at Node - if you have a concrete proposal. However, I have to say chances are pretty slim. |
@benjamingr OK then. |
@itaysabato sure, and sorry for losing :) |
#goodnessSquad
The text was updated successfully, but these errors were encountered: