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

Continuation type encoding

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

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading the discussion in issue #89, then compare the three continuation type-index encodings listed here: u32, zero-valued u8 followed by u32, and s33. Done means reaching and documenting a decision about the encoding and its future extension implications.

Written by the indexing model from the issue text.

Description

This is a tracking issue to continue the discussion in #89.

We can encode the type (cont $ft) in different ways. The interesting part is the encoding of the type index $ft. Some possible ways we can encode the type index:

  • as a u32,
  • as a zero-valued u8 followed by a u32,
  • or as a s33.

The latter two options give a natural "extension" point, enabling us to attach additional metadata to continuation types in the future.

Dominant language
WebAssembly
Stars
216
Forks
19
PR merge metrics
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 WebAssembly/stack-switching

All issues in WebAssembly/stack-switching

Similar issues

More Compilers issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.