protocolbuffers / protocolbuffers/protobuf
inconsistent handling of keywords and conflicts
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 72k
- Forks
- 16.3k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 140
Description
Various code generators and languages have interesting non-overlapping sets of keywords. Protobuf as a whole does not handle these things consistently (sometimes it mangles them, sometimes it generates code that doesn't compiler). When the mangling causing conflicts with other feels we are one again inconsistent. Then we are sad.
What needs to happen is a systematic push to
- figure out what we do now
- propose a unified solution
- move things to it
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 names no files, tests, or entry points; begin by inventorying how keyword mangling and conflicts are currently handled across the code generators and languages. Document a unified solution, then identify and migrate the inconsistent cases until the generators no longer produce conflicting or uncompilable code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100