planetscale / planetscale/vtprotobuf
Per Msg/Field Features
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 112
- PR merge metrics
- No merged PRs in 30d
Description
👋
Are there any plans to support adding features per-msg or per-field?
For example, for some of our string or []byte fields, we prefer to unmarshal them as "unsafe" so as to avoid an allocation if we don't plan to keep the data in memory past the lifetime of the original message.
I was thinking that type of behavior could be added as an annotation in the proto, similar to how the extensions in gogo currently work.
Is that something that is 1.) feasible with this project 2.) something that you would be interested in?
If so, I could try to come up with a POC
Thanks
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
The issue proposes per-message or per-field annotations for unsafe unmarshaling, but names no files, tests, or implementation entry point. First determine whether the requested proto annotation and generated-code behavior are feasible; done would require an agreed scope and a proof of concept, neither of which is specified here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100