WebAssembly / WebAssembly/shared-everything-threads

Is there a way to make i31 shared?

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

Nobody has claimed this yet.

Dominant language
WebAssembly
Stars
97
Forks
6
PR merge metrics
No merged PRs in 30d

Description

As @rossberg pointed out in https://github.com/WebAssembly/shared-everything-threads/pull/55#issuecomment-2088280990, it would be nice if we could allow i31ref in shared contexts. The trouble is that it would then have to be a subtype of both eqref and (shared eqref) (at least AFAICT), and we have never allowed a type to have multiple supertypes before, making this a risky new frontier. We should experiment with this and see whether we run into problems in practice.

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.

Research direction

Start with the issue text and the discussion linked in PR #55, focusing on the proposed shared-context behavior for i31ref and the implications of multiple supertypes. Done means determining through experimentation whether this type relationship works in practice without introducing problems.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.