WebAssembly / WebAssembly/wasi-keyvalue

Non string keys

Open
#8 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
54
Forks
18
PR merge metrics
No merged PRs in 30d

Description

There are many use-cases that would benefit from having a key-value store where keys are not strings but opaque bytes, would there be a particular reason why the type key needs to be string?

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

Start with the wasi-keyvalue API definition for the key type and review the issue discussion about opaque byte keys. Determine whether the API should support non-string keys and document the compatibility and usage requirements; done means the design question has a settled direction.

Written by the indexing model from the issue text.

Assessment

Tech stack
wasm
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.