WebAssembly / WebAssembly/wasi-keyvalue
Atomic and non-atomic operations on the same key
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 54
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Somewhat related to https://github.com/WebAssembly/wasi-keyvalue/issues/51: what are the semantics of having both e.g. successful set and swap operate on the same key at the "same time"?
A few options come to mind:
- Undefined (don't do that)
- Result is either the new
setvalue or the newswapvalue- or the old
swapvalue? 🤔
- or the old
- Namespace atomic keys;
set('foo')andincrement('foo')refer to two different keys
Any other options? I can't think of anything stronger that would be supported by enough implementations.
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 reading the related issue #51 and the three comments on this issue. The work is done when the project agrees on and documents a definitive concurrency semantic for atomic and non-atomic operations targeting the same key.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100