rust-lang / rust-lang/rust-bindgen
Add integration tests for Objective-C
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.3k
- Forks
- 829
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 15
Description
Currently, we don't test that our objective-c generated bindings actually work. Giving that we have to do lots of escaping for obective-c names that are keywords in rust, it would be good to test that such bindings work even when the names are escaped.
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 locating how Objective-C bindings are generated and where integration tests for generated bindings are organized. Cover names that require escaping because they are Rust keywords, and consider the work done when those generated bindings are compiled and exercised successfully by the integration tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- objective-c, rust
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100