Refactor method resolution code out of Compiler and into Reflector

Description

Issues:

  1. Code for obtaining method/constructor instances is duplicated across the Compiler

  2. Code for resolving a preferred overloaded method lives in the Compiler

By consolidating the duplicated code, moving the reflection-related parts into Reflector, and providing a straightforward API, it should be easier to read and understand the method resolution process. Further, improvements to (e.g., CLJ-445) the mechanism for reflecting on class members can largely be isolated from the Compiler. And the few points of coordination (e.g., Compiler emitting same arg and return types as Reflector does when invoking) can be clearly identified and documented.

Environment

None

Assignee

Unassigned

Reporter

Alexander Taggart

Labels

None

Approval

None

Patch

None

Priority

Major
Configure