Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support type annotation in WAC

Open
#57 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust, wasm
Domain
tooling

Research direction

Start by reading issue #56 and the component-instantiation path related to WIT generated by witgen. Trace how the unknown import error is produced and determine the expected type-annotation behavior; the work is done when intended imports and exports can be fixed by an annotation without the erroneous diagnostic.

Written by the indexing model from the issue text.

Description

When instantiating a component, it's useful to allow the user to provide type annotation that fixes the component's expected imports and exports. For example, in the scenario described in #56, the type annotation can be used to suppress the unknown import error when the import is intended but is not present in the component's WIT, generated by witgen.

Dominant language
Rust
Stars
207
Forks
41
Avg merge
4d 9m
Merged PRs (30d)
4

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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/wac

All issues in bytecodealliance/wac

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.