Skip to content

Commit 7b4d8c5

Browse files
committed
Expand reasoning about why resource type defs are disallowed in type context
1 parent 9ec5829 commit 7b4d8c5

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

design/mvp/Explainer.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -777,8 +777,10 @@ declarators to be used by subsequent declarators in the type:
777777
```
778778

779779
The `type` declarator is restricted by validation to disallow `resource` type
780-
definitions. Thus, the only resource types possible in an `instancetype` or
781-
`componenttype` are introduced by `importdecl` or `exportdecl`.
780+
definitions, thereby preventing "private" resource type definitions from
781+
appearing in component types and avoiding the [avoidance problem]. Thus, the
782+
only resource types possible in an `instancetype` or `componenttype` are
783+
introduced by `importdecl` or `exportdecl`.
782784

783785
With what's defined so far, we can define component types using a mix of type
784786
definitions:

0 commit comments

Comments
 (0)