bytecodealliance / bytecodealliance/cap-std
Change `Pool` to hold a callback instead of a set of grants?
- Dominant language
- Rust
- Stars
- 821
- Forks
- 57
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 4
Description
In https://github.com/bytecodealliance/wasmtime/pull/7662, there is discussion that a callback would be more useful than a simple set of allowed addresses. If that's true for Wasmtime, then it's true for cap-std in general, so we should consider migrating cap-std in that direction too.
The current code that maintains a list of allowed addresses could be factored out into a utility that users could use to implement the callback if they need that functionality.
Contributor guide
Research direction
Read the discussion in Wasmtime PR 7662, then inspect cap-std's current code that maintains the list of allowed addresses. Determine whether Pool should accept a callback and whether the existing address-list behavior should become a reusable utility; done requires a settled API direction and corresponding implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100