Skip to content

Commit

Permalink
Fix explanation of world encoding
Browse files Browse the repository at this point in the history
  • Loading branch information
lukewagner committed Sep 20, 2023
1 parent 968ff9a commit 7842b8f
Showing 1 changed file with 4 additions and 5 deletions.
9 changes: 4 additions & 5 deletions design/mvp/WIT.md
Original file line number Diff line number Diff line change
Expand Up @@ -1521,11 +1521,10 @@ is encoded as:
(export "the-world" (type $the-world))
)
```
In the current version of WIT, `world`s cannot contain `use` and thus the outer
wrapping component-type will only ever contain a single `export`. However,
as higher-order component use cases are supported by WIT (leading to worlds
importing worlds), `use` may be useful and added, thus adding imports to the
outer wrapping world.
In the current version of WIT, the outer wrapping component-type will only ever
contain a single `export` and thus only serves to separate the kebab-name
export from the inner exported interface name and to provide consistency with
the encoding of `interface` shown above.

When a world imports or exports an interface, to produce a valid
component-type, the interface's compiled instance-type ends up getting copied
Expand Down

0 comments on commit 7842b8f

Please sign in to comment.