use AbiKind term more
Open
Nobody has claimed this yet.
- Dominant language
- reStructuredText
- Stars
- 497
- Forks
- 41
- Avg merge
- 3h 52m
- Merged PRs (30d)
- 4
Description
Would like to, in future, use AbiKind, which is defined as the "C" in extern "C". This will also help, in future, if we move to edition 2024, which requires unsafe be specified (like unsafe extern "C").
Originally posted by @tshepang in https://github.com/rust-lang/fls/issues/630#issuecomment-3650855877
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 uses of AbiKind and extern "C" in the FLS text, then review how the ABI kind is described. Done means the relevant terminology consistently uses AbiKind and remains compatible with the noted Rust 2024 unsafe extern syntax.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100