rust-lang / rust-lang/rust-bindgen
Constants like UINT64_MAX not recognized, even with clang_macro_fallback
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.3k
- Forks
- 829
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 15
Description
Although #1636 was fixed, using builder.clang_macro_fallback() does not work with macros that expand to values that do not fit in a u32. It is potentially related to #2618.
// header.h
#include <stdint.h>
#define FOO (UINT32_MAX)
#define BAR (UINT32_MAX)
// bindings.rs
pub const FOO: u32 = 4294967295;
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 with the builder.clang_macro_fallback() entry point and reproduce the issue using the header.h and bindings.rs snippets. Trace how macro values larger than u32 are handled, and consider the relationship to issues #1636 and #2618. Done means the generated binding represents the macro value correctly without the reported limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100