WebAssembly / WebAssembly/custom-page-sizes

Update the memory abbreviation in the text format

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

Nobody has claimed this yet.

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

Description

The current proposal for the extension of the memory abbreviation does not take into consideration the memory64 feature and the existence of an addrtype:

The memory abbreviation is extended to allow an optional page size as well:

'(' 'memory' id? mempagesize? '(' 'data' b_n:datastring ')' ')' === ...

Is mempagesize? supposed to be before or after addrtype? ?

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 linked WebAssembly text-format specification section for the memory abbreviation, then compare the roles of mempagesize and addrtype in the memory64 proposal. Determine whether the grammar places mempagesize before or after addrtype and document the resulting ordering decision.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.