diff options
author | brandjon <brandjon@google.com> | 2018-06-25 09:34:55 -0700 |
---|---|---|
committer | Copybara-Service <copybara-piper@google.com> | 2018-06-25 09:36:49 -0700 |
commit | cb68a96f1a359ee59cf02a2ffd220b2dbcb95b6e (patch) | |
tree | 9cd1c18a9b2dc8611b95cde0f780ed6ffac49991 /site | |
parent | cac65060368ad57e038b59ec185ef816bef9c7e6 (diff) |
Clarify that depset order is deterministic
In response to https://github.com/bazelbuild/rules_scala/issues/531
RELNOTES:
PiperOrigin-RevId: 201966809
Diffstat (limited to 'site')
-rw-r--r-- | site/docs/skylark/depsets.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/site/docs/skylark/depsets.md b/site/docs/skylark/depsets.md index 570ac23211..95ae9a62a4 100644 --- a/site/docs/skylark/depsets.md +++ b/site/docs/skylark/depsets.md @@ -284,7 +284,8 @@ print(create("topological").to_list()) # ["d", "b", "c", "a"] 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 |