Test that all functions are wrapped in a panic boundary
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 170
- Forks
- 43
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 10
Description
Followup from https://github.com/abetterinternet/crustls/pull/25. We should have automated tests to ensure newly added functions are treated with an ffi_panic_boundary_* macro.
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 reading the follow-up context in PR #25 and inspect the Rust FFI functions discussed there. Determine how automated tests can identify functions missing an ffi_panic_boundary_* macro, then verify that the tests catch newly added unwrapped functions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100