stacks-network / stacks-network/stacks-core
refactor: explore cancellation token idea for static analysis and evaluation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.1k
- Forks
- 762
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 76
Description
The idea is to evaluate to refactor code in analyze_smart_contract and initialiaze_smart_contract (and possibly any related code working with eval, and execution timer) around a cancellation token concept.
Some food for thought has been shared in this comment https://github.com/stacks-network/stacks-core/pull/7349#discussion_r3494712335, when introducing the time tracker for contract analysis.
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 analyze_smart_contract and initialiaze_smart_contract code, then review the linked pull-request discussion about the time tracker for contract analysis. Determine the scope and expected behavior of a cancellation-token approach for analysis, eval, and execution timing before defining what a completed refactor would require.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain, compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100