FR: allow schema evolution (in or after 0.6)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No files, tests, or entry points are named. Start by reading the existing bitcode encoding, especially the 0.6 style, then clarify compatibility and defaults for appended struct fields, enum variants, and increased integer capacity; the work is done only after a concrete schema-evolution design and scope are agreed.
Written by the indexing model from the issue text.
Description
I know it would be serving really different audience if it supports schema evolution (SE for short). But I would really benefit from similar encoding as bitcode but with SE and it would be a lot of duplicate code to implement such thing. So I'm here to ask: will you consider adding SE as a flavor of bitcode? Or somehow allow me to write a crate that easily reuses bitcode encoding and add SE?
I think the main thing that schema evolution need is
- appending fields to struct (the encoding will store the number of fields in struct and new fields will be deserialized to default)
- appending variant to enum
- increase capacity of ints (I.e. u8 to u16) (though this is less important)
In 0.6 style encoding, this would not add much space either.
- Dominant language
- Rust
- Stars
- 673
- Forks
- 61
- 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 SoftbearStudios/bitcode
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
SoftbearStudios/bitcode#122 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
SoftbearStudios/bitcode#121 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
SoftbearStudios/bitcode#115 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
SoftbearStudios/bitcode#110 · 1 reaction ·
-
BUffer for serde?May be free again @caibear claimed this 224 days ago, and no pull request is open. Open
SoftbearStudios/bitcode#102 · 1 comment · 1 assignee ·
All issues in SoftbearStudios/bitcode
Similar issues
-
Change output crossing a compactsize boundary leaves the fee slightly below the requested feerateOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bitcoindevkit/bdk_wallet#578 ·
Maintainers usually reply within 8 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
521xueweihan/HelloGitHub#3832 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
canonical/opentelemetry-collector-operator#409 ·
Maintainers usually reply within 1 day