design/ clarify replace example

Change-Id: I515292cd1182c7a777255511ea4c7dd7559da8b3
Trust: Michael Matloob <>
Run-TryBot: Michael Matloob <>
Reviewed-by: Michael Matloob <>
diff --git a/design/ b/design/
index 14638ea..ebe2a10 100644
--- a/design/
+++ b/design/
@@ -193,7 +193,7 @@
 replace (
- => ./tools
+ => ../tools v0.4.1  => v0.5
@@ -491,8 +491,11 @@
 build them. Not respecting them would break users unnessesarily. `replace`
 directives exist in the workspace file to allow for resolving conflicts between
 `replace`s in workspace modules. Because all workspace modules exist as
-co-equals in the workspace, there is no other clear and intuitive way to resolve
-`replace` conflicts.
+co-equals in the workspace, there is no clear and intuitive way to resolve
+`replace` conflicts without explicit input from the user. One alternative is
+to add special syntax for overriding replaces to make the overriding behavior
+more explicit, and an additional option is to add an option to add syntax to
+nullify replaces without overriding them.
 Working in modules not listed in the workspace file is disallowed to avoid what
 could become a common source of confusion: if the `go` command stayed in