rust-lang / rust-lang/rust-bindgen
Using the github repo version of `bindgen` points to a very old version.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.3k
- Forks
- 829
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 15
Description
It is a common pattern to use the git repo of a dependency to try new features that have not been released yet. So it would be normal for users to add the following in their cargo manifest:
[build-dependencies]
bindgen = { git = "https://github.com/rust-lang/rust-bindgen" }
However that would actually fetch the HEAD branch whose last commit is from 2019. Users would have to add the following then:
[build-dependencies]
bindgen = { git = "https://github.com/rust-lang/rust-bindgen", branch = "main" }
Or even branch = "master". I wonder if there's a reason why this HEAD branch exist and if we should document how to use "the latest" bindgen somewhere.
cc @emilio @amanjeev @kulp
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
Start by checking how the repository's default branch resolves the Cargo git dependency shown in the issue, then compare that with the main and master examples. Confirm the intended way to obtain the latest bindgen source and document that usage, including why the default HEAD reference is stale if that remains true.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- build-system, tooling
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100