WebAssembly / WebAssembly/component-model

Question: Specialized value types

Open
#319 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
WebAssembly
Stars
1.4k
Forks
130
Avg merge
2d 1h
Merged PRs (30d)
15

Description

Looking at: https://github.com/WebAssembly/component-model/blob/main/design/mvp/Explainer.md?plain=1#L638-L653 it shows that a string should be despecialized to a list<char>, but it is not implemented like that in definitions.py, is that a conflict?

Contributor guide

No contributing guide indexed for this repository

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

Read the cited lines in design/mvp/Explainer.md and inspect definitions.py to compare how specialized string values and list are represented. Determine whether the difference is intentional or an implementation/specification mismatch; done means the discrepancy and required follow-up are clearly established.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, wasm
Domain
compilers
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.