Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reachability ideas #8

Open
pettermahlen opened this issue Jun 11, 2015 · 1 comment
Open

Reachability ideas #8

pettermahlen opened this issue Jun 11, 2015 · 1 comment

Comments

@pettermahlen
Copy link
Member

We could probably improve the reachability logic a bit.

  • If a class is referenced somewhere, we should visit the static initializer method
  • If a class is instantiated somewhere, we should visit all non-static methods (because we can't really know when they're going to be invoked because of external interfaces and inheritance)
  • Static methods should only be visited when they're actually called.
@pettermahlen pettermahlen changed the title Reacab´´ Reachability ideas Jun 11, 2015
@pettermahlen
Copy link
Member Author

This (and maybe more) would probably be solved by proguard #9. That's not necessarily the best solution, but one solution at least.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant