rust-lang / rust-lang/rust-bindgen
Consider rewriting the parsing back-end as a clang plugin instead of using libclang.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.3k
- Forks
- 829
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 15
Description
This would be sort of a pain, but it's the only way we see us generating more correct code for all the partial template specialization madness we're going through with m-c. I already discussed this in #41 and similar IIRC.
We would need to comunicate with the front-end of course, we could do that via json or similar.
I might introduce an experimental back-end for this if I have the time and we keep breaking stylo.
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
No file or test is named. Start by reading the existing libclang parsing backend and the discussion in issue #41, then trace how the parser communicates with the front-end. Done would require an agreed clang-plugin backend boundary, including the proposed JSON-style communication and handling of partial template specializations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, rust
- Domain
- compilers, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100