WebAssembly / WebAssembly/threads
Consolidate agent/agent cluster definitions with ES spec?
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 767
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
See also https://github.com/tc39/ecma262/issues/887. This is mostly a concern for when this gets to the level of formal specification, not during the design phase.
It seems like it'd be a bad end state for two separate specs to define these concepts, when they're meant to operate on the same level. There are a variety of solutions here, but the one that seems easiest is to send appropriate PRs to the ES spec to make sure their concept is general enough, and then reference them.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked TC39 issue 887 and the proposal's discussion of agent and agent cluster definitions. Determine whether the concepts should be consolidated through changes to the ES specification or by cross-referencing it. Done would require an agreed specification approach and the appropriate ES-spec changes or references.
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
- 20/100