Vector35 / Vector35/binaryninja-api
Add 'restrict' concept to type system
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Not sure on the design yet, but in particular to help ameliorate situations like those caused by https://github.com/Vector35/binaryninja-api/issues/4544 we should have the ability to override the improved alias tracking that disables data flow in cases where the user wishes to ignore the aliasing and allow data flow.
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 reading issue 4544 and the existing alias-tracking and type-system behavior described here. The design is not settled, so first define how a user would override alias-based data-flow restrictions and what observable behavior would demonstrate that the restrict concept is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100