`Execute.tiering` should not be global
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 512
- Forks
- 51
- Avg merge
- 7h 34m
- Merged PRs (30d)
- 21
Description
Currently Execute.tiering is a global flag referenced by all instances of Wasm stacks and the runtime. This makes extending ExeTester difficult as Execute.tiering can be set in arbitrary order when running the tests (its constructor sets Execute.tiering). I think we should look into refactoring away this global state.
Contributor guide
No contributing guide indexed for this repository
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 tracing Execute.tiering through ExeTester, the Wasm stacks, and the runtime to identify how instances share and set the flag. Determine the configuration boundary needed to remove the global state, then verify that tests no longer depend on constructor or execution order and that each instance uses its intended tiering setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100