techyCoder81 / techyCoder81/smashnet
progress callback cannot use closures that capture their environment
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
the progress callback should be improved so that closures which capture their environment can be used. This will require some potentially unsafe shenanigans, but will be better overall.
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 by locating the progress callback implementation and tracing how it accepts and invokes callbacks. Determine the ownership and lifetime constraints for closures that capture their environment, then define tests showing that such closures can be registered and called successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100