You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: component-model/src/reference/faq.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ set of exports ([legacy specification][wasi-p1]).
43
43
44
44
WebAssembly core modules use functions provided by the host system (the "outside world") but they can only perform
45
45
computations on a fixed set of primitive types (`i32`, `i64`, `f32`, `f64`), `v128`). The component model enables core components to interact with the "outside world"
46
-
world via a rich set of types ([WebAssembly Interface Types][wit]).
46
+
via a rich set of types ([WebAssembly Interface Types][wit]).
47
47
48
48
Where as WebAssembly core components must find a way to represent higher level types with the primitives defined in an ad hoc manner, the Component Model presents a consistent way of representing complex types familiar in most high level languages.
0 commit comments