From 8e0cfff279e05f66bd1aab4445c34f50abf9f234 Mon Sep 17 00:00:00 2001
From: ykjchen <4423897+ykjchen@users.noreply.github.com>
Date: Sat, 10 Oct 2020 11:04:59 -0700
Subject: [PATCH] Add documentation to +all: that clarifies the order in which
 promises are resolved and their position in the returned array.

---
 g3doc/index.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/g3doc/index.md b/g3doc/index.md
index e2a70db..ae2bb9b 100644
--- a/g3doc/index.md
+++ b/g3doc/index.md
@@ -1025,6 +1025,12 @@ they've been fulfilled, the promise returned from `all` is fulfilled with an
 array of all fulfilled values. If one of the given promises is rejected, then
 the returned promise is rejected with the same error.
 
+Note that `all` does not control when each contained promise task starts
+(a promise task starts when that promise is created), nor when each promise
+is resolved (this depends on the length of the task). However, it does
+guarantee that the order of promises in the output array is identical to the
+order of promises passed to it in the input array.
+
 In Swift, the `all` operator also allows passing promises of heterogeneous
 types. For this case, the returned promise will be resolved with a tuple
 containing the values of the input promises in the same order they were