rust-lang / rust-lang/rust-bindgen
Improve macro defined constants to recognize #define CONSTANT ((int) 1)
Open
Nobody has claimed this yet.
A-macros
enhancement
help wanted
rust-for-linux
- Dominant language
- Rust
- Stars
- 5.3k
- Forks
- 829
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 15
Description
In the header files I am trying to make bindings for, some constants are defined like this:
#define kOfxStatFailed ((int)1)
#define kOfxStatErrFatal ((int)2)
// ...
Can this pattern be supported? Maybe I can attempt to add this if I get some guidance :)
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 in the issue. Start by locating bindgen's handling of C preprocessor constants and existing cast-related cases, then trace how generated bindings represent integer macros. Done means definitions such as ((int)1) and ((int)2) are recognized and produce usable bindings, with coverage for the reported pattern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100