Go-datastore and return values
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading the Datastore.Get and Put interface definitions and the repository's datastore documentation, if present. Determine whether type allocation and marshaling belong to the datastore or its clients, then document or propose a settled contract that explains how arbitrary Go values are stored and retrieved.
Written by the indexing model from the issue text.
Description
Datastore.Get returns its result as a return value, which means that the Datastore implementation needs to allocate it. But if one wishes to store arbitrary types of data into a datastore, how can Get know what type of value to allocate? The only ways I can think of are
- either the Datastore implementation needs to memoize the reflect.Type of every value as it is Put, so it can recall the type based on the key when it is Get, or
- the Datastore implementation takes on initialization a mapping from key prefixes/types/something else to reflect.Types, so it can again determine the correct type to allocate based on the key,
but these would bring considerable complexity to any Datastore implementation that wishes to allow storage and retrieval of arbitrarily typed data. Am I missing something obvious, or is this by design? Should any unmarshaling from datastore representations to Go objects (and vice versa) be the client code's responsibility?
- Dominant language
- Go
- Stars
- 248
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from ipfs/go-datastore
-
exp/novice help wanted kind/enhancement status/ready
Difficulty 5/5 Over a week Newbie friendliness 25/100
ipfs/go-datastore#160 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ipfs/go-datastore#139 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ipfs/go-datastore#116 · 31 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
ipfs/go-datastore#102 · 5 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
ipfs/go-datastore#101 · 4 comments · 1 reaction ·
All issues in ipfs/go-datastore
Similar issues
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
harvester/harvester#12311 · 1 comment ·
Maintainers usually reply within 1 day
-
verifyrun --bracket-digest --credit: relative --witness is could-not-check, absolute path creditsOpenbug effort:s impact:low raised-by:desk risk:low
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
medici-finance/assay#6580 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
blinklabs-io/gouroboros#3026 ·
Maintainers usually reply within 1 day