stacks-network / stacks-network/stacks-core
Illegal use of reserved keywords should be caught during contract analysis
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.1k
- Forks
- 762
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 76
Description
There is a lot of discussion on this issue on the blockchain repo: https://github.com/stacks-network/stacks-blockchain/issues/3176
I will not duplicate all of it here, but the question is about whether the builtin functions and keywords should be reserved or if they can be freely used as variable and function names. Regardless of the answer to that question, we should ensure that the analysis-time behavior is the same as the run-time behavior.
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 discussion in stacks-blockchain issue 3176, then trace how reserved keywords and builtin functions are handled during contract analysis and at runtime. Done means the analysis-time behavior consistently matches the runtime behavior, with the reservation policy resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain, compilers
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100