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: examples/go_component/README.md
+84Lines changed: 84 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,6 +107,90 @@ go_wasm_component(
107
107
-**Composability**: Link multiple components together
108
108
-**Language Interop**: Call between Go, Rust, C++, JavaScript components
109
109
110
+
## TinyGo WASI Runtime Requirement
111
+
112
+
### Why TinyGo Components Always Need WASI
113
+
114
+
Unlike C/C++ or Rust, **TinyGo reactor components (even with empty `main()`) require WASI imports**. This is due to TinyGo's Go runtime architecture, not a Component Model limitation.
115
+
116
+
**TinyGo Runtime Architecture:**
117
+
- TinyGo's Go runtime is built on WASI primitives for system operations
118
+
- Even reactor components with `func main() {}` trigger runtime initialization
0 commit comments