Add `AllSettled` method to package. about promise HOT 12 CLOSED

Yes, you are quite right
I think we should research how this method is implemented in another languages since it's only a draft / proposal in JS

from promise.

This actually looks pretty good:
https://github.com/tc39/proposal-promise-allSettled#examples
https://github.com/tc39/proposal-promise-allSettled#real-world-scenarios

from promise.

Right, I agree.
I'll start up a new branch for it shortly 👍 ,

from promise.

Thanks for creating this issue. I read the code from the Race PR where you started working on the AllSettled method. Could you explain the reasoning behind the Result type and why it's needed? Reading the spec I see the following Returns ... an array of objects that each describe the outcome of each promise. meaning that AllSettled[Promise("hello"), Promise("world"), Promise(willError)] will return ["hello", "world", someError] and the user can do a for loop and switch on each element's type

from promise.

Sure, not a problem 👍 .
If you run the example on the mdn site with the following change:
console.log(result.status) to console.log(result) you'll see that result is actually
an object. Link: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/allSettled

from promise.

Woops, also seems only chrome 76 and up currently supports Promise.allSettled,

from promise.

Though also, if you see the line (in the example (mdn example)) you'll see they're actually referencing the contained promise status via result.status (hence what I did)).

from promise.

Ah, here is a good description (from the 'allSettled' draft):
https://tc39.es/proposal-promise-allSettled/

from promise.

I think we should do it your way, the way JS drafted it with the results objects (status, value, reason), so it's consistent and follows the design

from promise.

I've decided to avoid the result object way until we get proper generics in Go 2.0 because the result type is lost due to interface{} return value of the promise.

Right now the user should type switch on the returned value (error or some known-to-user type)

from promise.

Aha, I didn't think about that before haha, yes I agree. Result is lost and is hard to know what is returned unless written in docs (I.e., the only way to know is via docs). Good work 👍 .

from promise.

Thanks a lot for pointing out the way JS implements this.
I definitely want to come back to that when we get generics and the type will no longer be lost.

from promise.