Document #[no_mangle] requirement in assert-instr / stdsimd-test
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 694
- Forks
- 336
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 9
Description
@alexcrichton wrote: Handle debuginfo weirdness by flagging functions as no_mangle that
we're looking for instructions within.
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 the assert-instr and stdsimd-test entry points and reviewing how the no_mangle requirement is currently handled. Document why functions searched for instructions need no_mangle, with the relevant usage clearly identified; the documentation is done when a contributor can understand and follow that requirement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation, testing
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100