AccessKit / AccessKit/accesskit-c
ABI stability?
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 32
- Forks
- 7
- Avg merge
- 28m
- Merged PRs (30d)
- 3
Description
Looking at accesskit.h, there's no VERSION macros and the enums don't have hardcoded values. Is there a stable API or ABI here? Will enum values, data structures or function signatures change?
Contributor guide
No contributing guide indexed for this repository
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 accesskit.h and inspect how enums, data structures, function signatures, and versioning are currently exposed. Define the project's supported API and ABI stability policy, then document the compatibility expectations; the issue is done when those guarantees are explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust
- Domain
- api
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100