Skip to content

Commit 5f4f5e0

Browse files
Mossakalukewagner
andauthored
Update design/mvp/WIT.md
Co-authored-by: Luke Wagner <[email protected]>
1 parent 2d7e6f2 commit 5f4f5e0

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

design/mvp/WIT.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -338,10 +338,7 @@ world union-my-world-b {
338338

339339
### Name Conflicts and `with`
340340

341-
When two or more included Worlds have the same name for an import or export, the name is considered to be in conflict. The conflict needs to be explicitly resolved by the world author using the `with` keyword. `with` allows the world author to rename the import or export to a different name.
342-
343-
Notice that when import or export names are IDs and since IDs are unique, there is no need to resolve name conflicts. Thus the `with` syntax is invalid when used with `include <ID>`. Only when import or export names are kebab names, name conflicts need to be resolved.
344-
341+
When two or more included Worlds have the same name for an import or export that does *not* have an ID, automatic de-duplication cannot be used (because the two same-named imports/exports might have different meanings in the different worlds) and thus the conflict has to be resolved manually using the `with` keyword:
345342
The following example shows how to resolve name conflicts where `union-my-world-a` and `union-my-world-b` are equivalent:
346343

347344
```wit

0 commit comments

Comments
 (0)