commit cb68a96f1a359ee59cf02a2ffd220b2dbcb95b6e
author brandjon <brandjon@google.com> Mon Jun 25 09:34:55 2018 -0700
committer Copybara-Service <copybara-piper@google.com> Mon Jun 25 09:36:49 2018 -0700
tree 9cd1c18a9b2dc8611b95cde0f780ed6ffac49991
parent cac65060368ad57e038b59ec185ef816bef9c7e6

Clarify that depset order is deterministic

In response to https://github.com/bazelbuild/rules_scala/issues/531

RELNOTES:
PiperOrigin-RevId: 201966809

site/docs/skylark/depsets.md

diff --git a/site/docs/skylark/depsets.md b/site/docs/skylark/depsets.md
index 570ac23..95ae9a6 100644
--- a/site/docs/skylark/depsets.md
+++ b/site/docs/skylark/depsets.md
@@ -284,7 +284,8 @@
 Due to how traversals are implemented, the order must be specified at the time
 the depset is created with the constructor’s `order` keyword argument. If this
 argument is omitted, the depset has the special `default` order, in which case
-there are no guarantees about the order of any of its elements.
+there are no guarantees about the order of any of its elements (except that it
+is deterministic).
 
 For safety, depsets with different orders cannot be merged with the `+` operator
 unless one of them uses the default order; the resulting depset’s order is the