Merge pull request #47 from asteurer/go-vet

feat: document how to use go vet

Author: asteurer

examples/wasip1/README.md

@@ -4,7 +4,7 @@
 
 ### Prerequisites
 
-- [**componentize-go**](https://github.com/bytecodealliance/componentize-go) - v0.3.0
+- [**componentize-go**](https://github.com/bytecodealliance/componentize-go) - Latest version
 - [**go**](https://go.dev/dl/) - v1.25+
 - [**wasmtime**](https://github.com/bytecodealliance/wasmtime)  - v43.0.0
 

examples/wasip2/README.md

@@ -4,7 +4,7 @@
 
 ### Prerequisites
 
-- [**componentize-go**](https://github.com/bytecodealliance/componentize-go) - v0.3.0
+- [**componentize-go**](https://github.com/bytecodealliance/componentize-go) - Latest version
 - [**go**](https://go.dev/dl/) - v1.25+
 - [**wasmtime**](https://github.com/bytecodealliance/wasmtime)  - v43.0.0
 
@@ -28,3 +28,15 @@ make run-tests
 make generate-bindings
 go test ./unit_tests_should_pass ./unit_tests_should_fail
 ```
+
+### Run `go vet`
+
+The generated code will fail the default `go vet` analysis due to:
+- How `unsafe.Pointer` is used
+- How the WIT tuple type is represented in Go
+
+If you must perform static analysis on the generated code, this is the workaround:
+
+```sh
+go vet -unsafeptr=false -composites=false ./...
+```

examples/wasip3/README.md

@@ -18,7 +18,7 @@ switch to the upstream releases.
 
 ### Prerequisites
 
-- [**componentize-go**](https://github.com/bytecodealliance/componentize-go) - v0.3.0
+- [**componentize-go**](https://github.com/bytecodealliance/componentize-go) - Latest version
 - [**wasmtime**](https://github.com/bytecodealliance/wasmtime)  - v43.0.0
 
 ### Build and Run