Decompose Outlining Transform

Open
#5,740 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
reverse-engineering

Research direction

Start by locating the current outlining transform in the decompiler pipeline and tracing the data it produces and consumes. Determine how it could be split into separate interposable transforms and what additional data the outlining process needs. Done means the pipeline uses the decomposed transforms and the existing outlining behavior remains covered by tests.

Written by the indexing model from the issue text.

Description

It would be an improvement to our decompiler pipeline if we decomposed the current outlining transform into a couple separate, interposable transforms. This would allow the transform to provide data that is useful for more than outlining. It would also allow the a part of the outlining process to consume some other data, which currently is not available when the outline transform runs.

Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Vector35/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.