Reusable stacks
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 360
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Hey!
First of all - awesome library, really useful for our project!
Second - we have a use case where we need to use a different stack then the one we execute it, but we don't want to create a new stack each time, so I thought maybe we would allocate it once then re-use it. I was wondering if you'd accept a PR adding this functionality.
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
No files, tests, or entry points are named in the issue. Start by locating the stack creation and execution APIs, then clarify the ownership and reuse behavior with maintainers; done would require an agreed design and tests covering reuse of an allocated stack.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100