Ali Rizvi-Santiago

The "persistence-refactor" branch is currently using `interface.access_t` to track both the modifications of an operand and any of the references. This is done with operands by returning an `interface.opref_t` which...

Currently this might be deprecatable due to #158. There's no way to control the order that plugins are loaded, but if ida-minsc controls the `idapythonrc.py` file, the user's `$HOME/.idapythonrc.py` file...

I'm pretty tired of writing documentation...

Just started working towards this..like 2 weekends ago iirc. It's not the exact solution, but it will end up being easier to maintain for a single human. I have the...

So far, the work on this seems to have been effective. The only thing that is missing are wrappers that enable the core logic to process more than just function...

Currently as per #158, the research into temporal modules has resulted in a solution for this using a proxy class (that maintains no internal state) which can change depending on...

The multicased function feature has been redesigned algorithmically. Although I don't think that having real-aliased namespaces is too important, this should definitely be worked on as it shouldn't be too...

Currently, I've switched away from using the `lvar_t` in favor of the `lvar_locator_t`. This is because if a function or its mba gets re-generated, the `lvar_t` goes out of scope....

Is there still help wanted on this issue?

Since PEP-3113 removed this, how would you expect this to appear? Would it appear as a unique Parameter.kind which can then be unpacked into their individual parameters via a `.__iter__()`...