WebAssembly / WebAssembly/WASI
Marking timezone as stable in 0.3?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
I don't know what's necessary for an interface to be considered stable. The timezone interface has been unstable since inception, and just got mostly revamped in https://github.com/WebAssembly/wasi-clocks/pull/71. Is it now ready to be stable? Does it need to have implementations first? I know there was some ongoing discussion in https://github.com/bytecodealliance/wasmtime/pull/6899.
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
Review the timezone interface changes in wasi-clocks pull request 71 and the ongoing discussion in Wasmtime pull request 6899. Determine the project's criteria for a stable interface and whether implementations are required; the issue is complete only when that stability decision is resolved and recorded.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100