Support language agnostic wit worlds

Open
#317 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, wasm
Domain
tooling

Research direction

Start by tracing the Go tooling that parses WIT worlds and generates bindings, then compare how other language toolchains handle worlds without an explicit wasi:cli/imports@0.2.0 include. Done means Go binding generation works for a world not designed specifically for Go without requiring that include.

Written by the indexing model from the issue text.

Description

Currently the world being targeted from Go has to explicitly include wasi:cli/imports@0.2.0;.
This is not a big deal when building a special world for Go, but becomes a problem when generating bindings to a world not designed with Go in mind.
It would be great it the Go tooling would match other language's tooling, and wouldn't require this include.

Dominant language
Go
Stars
148
Forks
20
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bytecodealliance/go-modules

All issues in bytecodealliance/go-modules

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.