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

Plan for enabling Wasm threads

Open
#124 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
wasm

Research direction

Start by reading WebAssembly/design#1261 and tc39/ecma262#1435 to understand the proposed SharedArrayBuffer and high-resolution timer changes. Compare how those plans affect Wasm's possible thread primitive, then document a resolved approach for enabling Wasm threads and the remaining questions.

Written by the indexing model from the issue text.

Description

From https://github.com/WebAssembly/design/issues/1261:

In https://github.com/tc39/ecma262/issues/1435 I detailed an approach the HTML community is planning on taking for reenabling ECMAScript's SharedArrayBuffer. This also affects Wasm if Wasm ever gets its own thread primitive (rather than building on top of workers and postMessage()) or some other high-resolution timer mechanism. Your input is most welcome.

Dominant language
WebAssembly
Stars
767
Forks
54
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/threads

All issues in WebAssembly/threads

Similar issues

More Operating Systems issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.