rust-lang / rust-lang/rust-bindgen
UINTMAX64 can never be generated
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.3k
- Forks
- 829
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 15
Description
Hi @emilio, while working on the fix for the case that wasn't handled in #2779, I noticed that bindgen can't support generating bindings for UINTMAX64. This is largely because all integers eventually get represented as an i64 so i64::MAX is the upper limit for u64 too. Is there any interest in a PR to support differentiating between u64 and i64 so that UINTMAX64 can be represented in bindgen?
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 reviewing the handling discussed in #2779 and the issue's description of integer values being represented as i64. Done means bindgen can generate a binding for UINTMAX64 while distinguishing u64 from i64.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100